Guest shutdown problems
by Christian Axelsson
Hello
I have a problem shutting down xen guests. Using xm shutdown guests get
shut down but gets stuck in state '---s-d' or sometimes '------'.
When trying to clone a domain when in this state (my original purpose of
the whole operation) I'll get the error:
[root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f
/var/lib/xen/images/new_img.img
ERROR: virDomainGetXMLDesc() failed failed Xen syscall
xenDaemonDomainDumpXMLByID failed to find this domain -490299505
The same errors occurs when for example trying to attach to the console
using virsh.
I have tried to use 'xm destroy' to kill the guest the hard way but it
has no effect - the state remains unchanged. I have also tried this on a
few different guest installations with the same result. A thing worth
noting is that the output from 'xm list --long' differs, I've attached
the out put pre boot, after boot and after shutdown. Note how all the
devices in the guests are missing after shutdown.
Both the hosts and the guests are fedora 8 installations.
Regards,
Christian Axelsson
smiler(a)lanil.mine.nu
[?1034h(domain
(domid 0)
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 2)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 16777215)
(memory 1491)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 1644.84369405)
(online_vcpus 2)
(image (linux (kernel )))
(status 2)
(state r-----)
)
(domain
(domid 2)
(on_crash restart)
(uuid a7638797-e237-3891-5e64-390f828238ca)
(bootloader_args )
(vcpus 1)
(name minimal)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 512)
(memory 512)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1206360333.14)
(cpu_time 9.753408915)
(online_vcpus 1)
(image
(linux
(kernel )
(notes
(FEATURES
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'
)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 18446744071562067968)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564189696)
(LOADER generic)
(SUSPEND_CANCEL 1)
(ENTRY 18446744071564165120)
(XEN_VERSION xen-3.0)
)
)
)
(status 2)
(state -b----)
(store_mfn 196619)
(console_mfn 196618)
(device
(vif
(bridge xenbr0)
(mac 00:16:3e:3f:93:b8)
(script vif-bridge)
(uuid 94afd732-920b-2e0b-b3d5-e79174754a80)
(backend 0)
)
)
(device
(vbd
(uname file:/var/lib/xen/images/minimal.img)
(uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd)
(mode w)
(dev xvda:disk)
(backend 0)
(bootable 1)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid 0046f2d3-058b-d524-9273-f1dac2ca950b)
)
)
)
[?1034h(domain
(domid 0)
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 2)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 16777215)
(memory 1491)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 1648.92600832)
(online_vcpus 2)
(image (linux (kernel )))
(status 2)
(state r-----)
)
(domain
(domid 2)
(on_crash restart)
(uuid a7638797-e237-3891-5e64-390f828238ca)
(bootloader_args )
(vcpus 1)
(name minimal)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 512)
(memory 512)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1206360333.14)
(cpu_time 13.048743365)
(online_vcpus 1)
(image
(linux
(kernel )
(notes
(FEATURES
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'
)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 18446744071562067968)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564189696)
(LOADER generic)
(SUSPEND_CANCEL 1)
(ENTRY 18446744071564165120)
(XEN_VERSION xen-3.0)
)
)
)
(status 0)
(state ---s-d)
(store_mfn 196619)
(console_mfn 196618)
)
[?1034h(domain
(domid 0)
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 2)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 16777215)
(memory 1491)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 1635.21430615)
(online_vcpus 2)
(image (linux (kernel )))
(status 2)
(state r-----)
)
(domain
(on_crash restart)
(uuid a7638797-e237-3891-5e64-390f828238ca)
(bootloader_args )
(vcpus 1)
(name minimal)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 512)
(memory 512)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1206309092.82)
(cpu_time 0.0)
(image
(linux
(kernel )
(notes
(FEATURES
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'
)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 18446744071562067968)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564189696)
(LOADER generic)
(SUSPEND_CANCEL 1)
(ENTRY 18446744071564165120)
(XEN_VERSION xen-3.0)
)
)
)
(status 0)
(device
(vif
(bridge xenbr0)
(mac 00:16:3e:3f:93:b8)
(backend 0)
(uuid 94afd732-920b-2e0b-b3d5-e79174754a80)
(script vif-bridge)
)
)
(device
(vbd
(uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd)
(bootable 1)
(driver paravirtualised)
(dev xvda:disk)
(uname file:/var/lib/xen/images/minimal.img)
(mode w)
(backend 0)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid 0046f2d3-058b-d524-9273-f1dac2ca950b)
)
)
)
14 years, 5 months
Problem with DomU networking
by Veli-Pekka Kestilä
Hi,
I have following problem with paravirtualised setup:
- Have Fedora 7 Dom0 (Yeah I know it's old, but haven't gotten
client to upgrade it yet to CentOS)
- DomU is CentOS5.2
On testing environment everything works fine, but in production CentOS
can't get ip-addess from Dom0
Strange thing is that FC7 client works without a problem with exactly
same xen config
From logs I can see that dhcpd server running on Dom0 sees the
DHCPREQUEST messages and answers to them, but DomU never recives them.
Greetings,
Veli-Pekka
14 years, 7 months
Should kernel 2.6.27.5-41.fc9 boot as xen guest?
by M A Young
I was trying to get a NVIDIA video driver working with the Fedora 9 kernel
2.6.27.5-41.fc9 (on x86_64) and it refused because it decided it was a xen
kernel, so I thought I would check this claim out.
My attempts to boot a xen guest with that kernel failed, though it got
past the boot loader stage, and I know Fedora 9 has kernel-xen packages,
but I was wondering whether this kernel would be expected to work or not.
Michael Young
14 years, 8 months
[ANNOUNCE] New release virtinst 0.400.1
by Cole Robinson
I'm happy to announce a new virtinst release, version 0.4.1. The release
can be downloaded from:
http://virt-manager.org/download.html
The direct download link is:
http://virt-manager.org/download/sources/virtinst/virtinst-0.400.1.tar.gz
This release includes:
- Add virt-image -> vmx support to virt-convert, replacing virt-pack
(Joey Boggs)
- Add disk checksum support to virt-image (Joey Boggs)
- Enhanced URL install support: Debian Xen paravirt, Ubuntu kernel and
boot.iso, Mandriva kernel, and Solaris Xen Paravirt
(Guido Gunther, John Levon, Cole Robinson)
- Expanded test suite
- Numerous bug fixes, cleanups, and minor improvements
Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!
Thanks,
Cole
14 years, 8 months
[ANNOUNCE] New release virt-manager 0.6.1
by Cole Robinson
I'm happy to announce a new virt-manager release, version 0.6.1. The
release can be downloaded from:
http://virt-manager.org/download.html
The direct download link is:
http://virt-manager.org/download/sources/virt-manager/virt-manager-0.6.1....
This release includes:
- VM disk and network stats reporting (Guido Gunther)
- VM Migration support (Shigeki Sakamoto)
- Support for adding sound devices to an existing VM
- Enumerate host devices attached to an existing VM
- Allow specifying a device model when adding a network device to an
existing VM
- Combine the serial console view with the VM Details window
- Allow connection to multiple VM serial consoles
- Bug fixes and many minor improvements.
Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!
Thanks,
Cole
14 years, 8 months
Re: [Fedora-xen] Goodbye Xen on RH/Fedora?
by Ján ONDREJ (SAL)
On Wed, Jan 21, 2009 at 12:19:31PM +0000, Richard W.M. Jones wrote:
> On Wed, Jan 21, 2009 at 01:12:52PM +0100, Jan ONDREJ (SAL) wrote:
>
> You have to tell the host to give the guest a virtio network card -
> change the NIC <model type='virtio'/> as described here:
Many thanks. Works well.
> http://libvirt.org/formatdomain.html#elementsNICS
There is nothing interesant on this URL. Part elementsNICS is not found,
but also thanks.
On Wed, Jan 21, 2009 at 01:23:06PM +0100, Emre Erenoglu wrote:
> you need to read the KVM virtio wiki pages, you need to disable that 8139
> emulated card driver (blacklist), then change some line in guest
> configuration file, and probe virtio driver at boot.
>
> http://wiki.libvirt.org/page/Virtio
>
> http://kvm.qumranet.com/kvmwiki?action=fullsearch&context=180&value=virti...
>
> find /lib/modules | grep virtio will give you the list of modules (if they
> are compiled as modules)
>
> You also need to have a recent kernel such as 2.6.25 which has built-in
> virtio support.
Thanks. I have it.
virtio_net works well, but I have trouble to boot from virtio_blk.
I can add second disk as virto block device, but I can't boot from first
disk. When using sedond disk, everything works well. When booting via grub,
this is on console:
input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/serio1/input/input3
Setting up hotplug.
Creating block device nodes.
Creating character device nodes.
Loading pata_acpi module
Loading ata_generic module
Loading virtio_blk module
Creating root device.
Mounting root filesystem.
mount: error mounting /dev/root on /sysroot as ext3: No such file or
directory
Setting up hotplug.
Creating block device nodes.
Creating character device nodes.
Loading pata_acpi module
Loading ata_generic module
Loading virtio_blk module
Creating root device.
Mounting root filesystem.
mount: error mounting /dev/root on /sysroot as ext3: No such file or
directory
I am using UUID in GRUB, my initrd has been regenerated with virtio_blk
module. I think, nash can't create /dev/vda* devices or something similar.
Any ideas, how to debug this or how to fix this?
SAL
14 years, 8 months
Goodbye Xen on RH/Fedora?
by Evan Lavelle
It seems I've been a bit thick. It's been pretty obvious recently that
Xen isn't flavour of the month around here, but I assumed there were
good reasons for that. Now, rather belatedly, I've found
http://www.redhat.com/about/news/prarchive/2008/qumranet.html
In short, RedHat paid $107 million for Qumranet in September 2008. The
acquisition includes KVM.
I've got 2 years invested in Xen, on FC8, and I can't help feeling that
I've been shafted. Am I alone?
-Evan
14 years, 8 months
Re: [Fedora-xen] Goodbye Xen on RH/Fedora?
by Daniel P. Berrange
On Wed, Jan 21, 2009 at 01:34:48PM -0500, Dustin Henning wrote:
> I tried the Qumranet drivers before I went with Xen. I don't think
> there is necessarily a problem with the Qumranet drivers, in fact, they
> could potentially have better inbound speeds than the GPLPV ones (though it
> seems unlikely as much as people test and James works on them on the
> xen-users list). The reason the Qumranet drivers don't cut it is because
> they are only network drivers. This means your data access (and possibly
> other stuff GPLPV hits) is still fully virtualized. Another reason I went
> with Xen is the PHY: option. I use a physical data source, as opposed to a
> file, for my guests. Each one has its own HD, actually, though partitions
> or RAID arrays would obviously work as well. If I remember correctly, when
> I tried this (some time ago), KVM had no such option.
KVM / QEMU don't make any artificial distinction between block devices
and files, like Xen did. You can use any block device, lvm volume or
file with QEMU / KVM - should be parity with Xen here.
Network driver is by far the most important one to virtualize since it
suffers much worse degradation when emulated, which is why PV net for
Windows was done as a priority. SCSI in QEMU should offer pretty good
performance - significantly better than IDE, and much closer to PV disk.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
14 years, 8 months
