Re: [Fedora-xen] Xen status for FC7
by fcxen user
Robert Story wrote:
> On Fri, 29 Jun 2007 19:17:54 -0700 FCXen wrote:
> F> > Are you sure you're not missing the domU's console? I noticed that with
> F> > at least the FC6 and F7 domUs, the boot output starts on the serial
> F> > console, then transfers to the graphical console. I'm not familiar with
> F> > the Centos domU's behavior, but it might be something to check.
> F>
> F> I think this is a big problem, it happened to me.* Unfortunately, I was trying
> F> on FC6 Test 2/3 so I was told to get the F7 release version and try that.
> F>
> F> There is no clear step by step how to on how to build GUI-less domUs for FC6
*
> F> or F7
>
> I simply edit the xen config file and comment out the virtual frame buffer
> line (vfb = [...]), and it works fine w/out a GUI...
How? For creating a domain, "we" (the headless/ssh/GUI-less/text-based people)
can't get through the creation process. And I thought that the F7 Xen didn't
have config files anymore, that it was all stored in an XML blob in a db
somewhere. Is that not the case?
I am pretty sure that it is not possible to do an interactive text based
creation of a F7 domU on an F7 dom0 via the virt-install command. And since I
posted my previous msg there have been at least 2 more people posting (here
and the Xen list) with the same problem AFAICT. I'll contact Thomas Chung
http://fedoraproject.org/wiki/ThomasChung when I get a chance and ask him to
create a Xen F7 QuickStart page so that it can get in the search engines and
people can find out that they need to use some other method for doing Xen
installs on F7. Unless there actually is a secret way to do it, if that is the
case I'll try to send him the actual step for people to follow.
* Sorry, I should have said specifically F7... I was testing on F6 test 2/3 so
those weren't really FC6.
16 years, 12 months
Xen status for FC7
by Frank Morane
Hi all,
I just did a fresh install of FC7 to see if xen would work out of the box.
Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU
boots but are unseable (after recompiling the initrd image with the xen
driver preloaded) up to the famous long lasting error message "4gb seg
fixup". At that point it is dead
My question: what id the status of Xen for Fc7? Will it ever fly?
Is there a Linux distro that works out of the box ?
The last usable version I saw was for FC5 as of May 2006, after that all
version were badly broken and never fixed, I tested ALL of them for
fc5/fc6 and not a single one worked as published. Only home brewed
compiled version would work after weeks of trial and error.
Here what the log says from my out of the box install:
[root@paine xen]# cat xend.log
[2007-06-29 08:08:34 2567] INFO (SrvDaemon:331) Xend Daemon started
[2007-06-29 08:08:34 2567] INFO (SrvDaemon:335) Xend changeset: unavailable.
[2007-06-29 08:08:34 2567] INFO (SrvDaemon:342) Xend version: Unknown.
[2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:126)
XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 35199342574L,
'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0,
'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1,
'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 962164L, 'handle':
[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name':
'Domain-0'})
[2007-06-29 08:08:35 2567] INFO (XendDomainInfo:143) Recreating domain
0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:2022) Storing VM
details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid':
'00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image':
'(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start':
'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus':
'1', 'vcpu_avail': '1', 'name': 'Domain-0'}
[2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:873) Storing domain
details: {'name': 'Domain-0', 'console/limit': '1048576', 'vm':
'/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
'cpu/0/availability': 'online', 'memory/target': '962164',
'control/platform-feature-multiprocessor-suspend': '1'}
[2007-06-29 08:08:35 2567] DEBUG (XendDomain:443) Adding Domain: 0
[2007-06-29 08:08:35 2567] DEBUG (XendDomain:379) number of vcpus to use
is 0
[2007-06-29 08:08:35 2567] INFO (SrvServer:180) unix
path=/var/lib/xend/xend-socket
[2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:873) Storing domain
details: {'name': 'Domain-0', 'console/limit': '1048576', 'vm':
'/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
'cpu/0/availability': 'online', 'memory/target': '962164',
'control/platform-feature-multiprocessor-suspend': '1'}
[2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:957)
XendDomainInfo.handleShutdownWatch
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VBD.set_device not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VBD.set_mode
not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VBD.set_type
not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VM.get_auto_power_on not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VM.set_auto_power_on not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VM.set_VCPUs_max not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VM.set_VCPUs_at_startup not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: debug.get_all
not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
console.get_other_config not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
console.set_other_config not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VIF.get_network not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
VIF.set_device not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VIF.set_MAC
not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VIF.set_MTU
not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
session.get_all_records not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call:
event.get_record not found
[2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: event.get_all
not found
[2007-06-29 08:08:46 2567] INFO (XMLRPCServer:149) Opening Unix domain
socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has
been disabled for this server.
[2007-06-29 08:08:46 2567] INFO (XMLRPCServer:149) Opening Unix domain
socket XML-RPC server on /var/run/xend/xmlrpc.sock.
Regards,
--
Frank Morane (Free Thinker)
http://www.adventuresinlegalland.com
http://www.lysanderspooner.org
http://thoreau.eserver.org
16 years, 12 months
Fedora Xen kernel
by John Lagrue
Because of complications with power management on my HP laptop, I
really need to run a 2.6.21 kernel (or later). Does anyone have any
idea when a Xen kernel will be available for that build? Currently the
Xen kernels are way out of date compared to the standard Fedora
kernels.
JDL
16 years, 12 months
XEN error with FC7
by Luc MAIGNAN
Hi,
I didn't succeed to install an FC7 guest on a FC7 host using
virt-install with nographics (the same operation with a FC6 was
successfull).
In the installation process, I've got first an error : libvir: Xen
Daemon error : GET operation failed:
and after a while, the installation hangs up.
ANy idea please ?
BR
16 years, 12 months
VCPUs >=2 will lead to failure of guest boot
by Songtao Liu
Hi,
As no one answer in list of xensource, I turn to here :)
still the question about VCPUs.
When I set VCPU >= 2, then I can not boot the guest.(the guest kernel is SMP)
Guest is 2.6.20-1.2952.fc6
When using Guest Winxp (VCPUs=2) it is OK.
How can I make it run with 2 VCPU :( ???
here is some other info: cpuinfo and xen configuration file.
Thanks in advance
Songtao
\Linux localhost.localdomain 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux
CPUinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz
stepping : 6
cpu MHz : 2168.162
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 5422.34
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz
stepping : 6
cpu MHz : 2168.162
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 5422.34
# Automatically generated xen config file
name = "system2"
builder = "hvm"
memory = "256"
disk = [ 'file:/home/songtao/Xen_Guests/Fedora6,hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:51:be:52, bridge=xenbr0', ]
uuid = "261877a2-1d16-8684-a66b-07170a381d6b"
device_model = "/usr/lib/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
vnc=1
vncunused=1
apic=1
acpi=1
pae=1
vcpus=2
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'
xend.log:
[2007-07-03 16:17:11 xend 2762] DEBUG (balloon:127) Balloon: 279472 KiB free; need 279144; done.
[2007-07-03 16:17:11 xend 2762] INFO (image:136) buildDomain os=hvm dom=1 vcpus=2
[2007-07-03 16:17:11 xend 2762] DEBUG (image:282) dom = 1
[2007-07-03 16:17:11 xend 2762] DEBUG (image:283) image = /usr/lib/xen/boot/hvmloader
[2007-07-03 16:17:11 xend 2762] DEBUG (image:284) store_evtchn = 1
[2007-07-03 16:17:11 xend 2762] DEBUG (image:285) memsize = 256
[2007-07-03 16:17:11 xend 2762] DEBUG (image:286) vcpus = 2
[2007-07-03 16:17:11 xend 2762] DEBUG (image:287) pae = 1
[2007-07-03 16:17:11 xend 2762] DEBUG (image:288) acpi = 1
[2007-07-03 16:17:11 xend 2762] DEBUG (image:289) apic = 1
[2007-07-03 16:17:11 xend 2762] DEBUG (image:435) hvm shutdown watch registered
[2007-07-03 16:17:11 xend 2762] DEBUG (blkif:24) exception looking up device number for hda: [Errno 2] No such file or directory: '/dev/hda'
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/768'} to /local/domain/1/device/vbd/768.
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:112) DevController: writing {'domain': 'winxp', 'frontend': '/local/domain/1/device/vbd/768', 'dev': 'hda', 'state': '1', 'params': '/home/songtao/Xen_Guests/winxp', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/768.
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:110) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0.
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'winxp', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:48:1a:3e', 'online': '1', 'frontend-id': '1', 'type': 'ioemu'} to /local/domain/0/backend/vif/1/0.
[2007-07-03 16:17:11 xend 2762] INFO (image:418) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '1', '-m', '256', '-boot', 'c', '-serial', 'pty', '-vcpus', '2', '-acpi', '-domain-name', 'winxp', '-net', 'nic,vlan=1,macaddr=00:16:3e:48:1a:3e,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vncunused', '-vnclisten', '127.0.0.1']
[2007-07-03 16:17:11 xend 2762] INFO (image:420) device model pid: 3708
[2007-07-03 16:17:11 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '4', 'uuid': '6d5f109d-cde9-aa57-65d8-48f824a06166', 'on_reboot': 'restart', 'start_time': '1183472231.33', 'on_poweroff': 'destroy', 'name': 'winxp', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '256', 'on_crash': 'restart', 'image': "(hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm) (pae 1) (vcpus 2) (boot c) (serial pty) (vnc 1) (vncunused 1) (display :0.0) (xauthority /root/.xauthP1IB4T) (acpi 1) (apic 1) (vncpasswd 'None'))", 'maxmem': '256'}
[2007-07-03 16:17:11 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:750) Storing domain details: {'console/port': '2', 'name': 'winxp', 'console/limit': '1048576', 'vm': '/vm/6d5f109d-cde9-aa57-65d8-48f824a06166', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '19693', 'cpu/1/availability': 'online', 'store/port': '1'}
[2007-07-03 16:17:11 xend 2762] DEBUG (image:458) hvm_shutdown fired, shutdown reason=None
[2007-07-03 16:17:11 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:143) Waiting for devices vif.
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:149) Waiting for 0.
[2007-07-03 16:17:11 xend 2762] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:486) hotplugStatusCallback 1.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices usb.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vbd.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:149) Waiting for 768.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:486) hotplugStatusCallback 1.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices irq.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vkbd.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vfb.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices pci.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices ioports.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices tap.
[2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vtpm.
[2007-07-03 16:17:12 xend 2762] INFO (XendDomain:370) Domain winxp (1) unpaused.
[2007-07-03 16:17:59 xend 2762] DEBUG (image:458) hvm_shutdown fired, shutdown reason=halt
[2007-07-03 16:17:59 xend.XendDomainInfo 2762] INFO (XendDomainInfo:899) Domain has shutdown: name=winxp id=1 reason=halt.
[2007-07-03 16:17:59 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=1
[2007-07-03 16:17:59 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:1471) XendDomainInfo.destroyDomain(1)
[2007-07-03 16:17:59 xend 2762] DEBUG (image:447) hvm shutdown watch unregistered
16 years, 12 months
libvir: Xen Daemon error : GET/POST operation failed:
by thewird
When I try to install a guest on 64bit FC7 I get the error below. Any
ideas?
# virt-install
Would you like a fully virtualized guest (yes or no)? This will allow
you to run unmodified operating systems. yes
What is the name of your virtual machine? fedora
How much RAM should be allocated (in megabytes)? 500
What would you like to use as the disk (path)? /dev/vg01/LVfedora
Would you like to enable graphics support? (yes or no) no
What is the virtual CD image, CD device or install location?
http://ftp.usf.edu/pub/fedora/linux/core/6/i386/os/
Starting install...
libvir: Xen Daemon error : GET operation failed:
Retrieving Fedora... 100% |=========================| 849 B
00:00
Retrieving boot.iso... 100% |=========================| 7.9 MB
00:12
libvir: Xen Daemon error : GET operation failed:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Device
5632 (vbd) could not be connected. losetup -r /dev/loop0
/var/lib/xen/virtinst-boot.iso.Kkp7nL failed')
Traceback (most recent call last):
File "/usr/sbin/virt-install", line 629, in <module>
main()
File "/usr/sbin/virt-install", line 578, in main
dom = guest.start_install(conscb,progresscb)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 649,
in start_install
return self._do_install(consolecb, meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 666,
in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 503, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirt.libvirtError: virDomainCreateLinux() failed POST operation
failed: (xend.err 'Device 5632 (vbd) could not be connected. losetup -r
/dev/loop0 /var/lib/xen/virtinst-boot.iso.Kkp7nL failed')
16 years, 12 months
64bit Hypervisor on 32bit OS
by thewird
I've been reading about how to make Xen show more then
16GB of ram and still support 32bit but so far all my
attempts have not worked. FC7 was supposed to be able
to run 32bit guests on its 64bit OS but because of a
feature freeze, this was not possible even though it
still says you can do it in the release notes which I
find ridiculous.
Anyway, someone told me if I replace the hypervisor
with the 64bit counterpart, then I should be able to
see more the 16GB of memory and be able to run 32bit
guests. I did this by extracting the files from the
64bit RPM and replaced the xen.gz-2.6.20-2925.11.fc7
file with the one from the 64bit RPM and rebooted. The
OS booted fine, however, when I tried
running/installing a 32bit domU the console would not
load or would lock up almost immediately.
I can't think of anything else to try and any help
would be greatly appreciated.
thewird
16 years, 12 months
VCPU number configuration
by Songtao Liu
Hi
as when I installed the XenU I initialized the VCPU=1, is it possible to change VCPU=2
Linux localhost.localdomain 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux
As far as I know from help, it seems impossible, see the last paragraph. But I dont want to install a new guest :(
vcpu-set domain-id vcpu-count
Enables the vcpu-count virtual CPUs for the domain in question. Like mem-set, this command can only allocate up to the maximum
virtual CPU count configured at boot for the domain.
If the vcpu-count is smaller than the current number of active VCPUs, the highest number VCPUs will be hotplug removed. This may
be important for pinning purposes.
Attempting to set the VCPUs to a number larger than the initially configured VCPU count is an error. Trying to set VCPUs to < 1
will be quietly ignored.
Thanks
Songtao
16 years, 12 months