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
xen kernel with dom0 in Fedora 10?
by David Hláčik
Hi , guys, I have found in Fedora 10 Features , that there is still a
lot of work to provide xen kernel with dom0 support to Fedora 10 GA.
For my future project, which at 90 percent depends on virtualization
technology I am deciding between XEN or KVM virtualization. I am
experienced XEN user, KVM is new for me. But as I am aware of,
Qumranet was bought by RedHat which predicts something ...
Thanks in advance!
David
14 years, 12 months
Re: [Fedora-xen] problems with f9 guest on f8 dom0
by Dale Bewley
----- "Matt Cowan" <cowan(a)bnl.gov> wrote:
> On Sat, 13 Sep 2008, Fred Brier wrote:
> > Subject: Re: [Fedora-xen] problems with f9 guest on f8 dom0
> >
> > I am using 32 bit and have the same issue you were. Did you ever
> solve the
> > problem? If so, how? Or should I just run Fedora 8 domU(s). Thank
> you.
>
> Haven't solved it yet, and have been totally unable to usefully run f9
> domU on an f8 dom0.
>
> We can get an f9 domU to install and run, but once it's shutdown,
> dom0
> needs a reboot for virt-install or virt-manager to function again,
> which is basically useless except for testing. 'xm' seems to
> continue
> funtioning fine. Just tried again last week after installing the
> latest
> round of xen related updates... still no luck.
>
> Gonna try 64bit next, and if that doesn't work, centos dom0 :(
> Is *anyone* out there running 32bit f8 dom0 and f9 domU without
> problems?!
> -matt
I'm continuing to run 64b F8 dom0 and F9 domU without any need to reboot the dom0 after bouncing a domU, but I do have to restart xend. My problem also affects F8 domUs. I've noticed, it seems, if I use xm commands to shutdown and startup then virt-manager retains track of the domU.
https://bugzilla.redhat.com/show_bug.cgi?id=453276
The last 2 libvirt updates have not been built for F8, so I'm not sure if there is any progress on the issue.
https://www.redhat.com/archives/libvir-list/2008-September/msg00401.html
I'm not interested in switching to CentOS or RHEL until I'm "forced" by circumstances or rationality. I'd prefer to support Fedora. Theoretically F8 still gets updates until around Dec, 25 2008 right now.
https://fedoraproject.org/wiki/Schedule#Fedora_10_Release_Schedule
There is a lot of impressive work going on with libvirt and virt in general from RedHat/Fedora, so I'm trying to be patient. I have a tenable workaround for now. Fingers crossed for F10.
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
15 years
problems with f9 guest on f8 dom0
by Matt Cowan
Anytime I shutdown or restart (the guest will successfully restart) an
f9 guest on an f8 dom0 it causes virt-manager to hang and virt-install
to fail. Attempts to restart virt-manager hang at "Connecting". no
luck restarting xend, libvirtd, or even xenstored, only solution I've
found is a dom0 reboot! Same problem on 2 different host systems,
different hardware, dom0 installed by different people. I have no
trouble with <=f8 guests on either of these boxes.
more details at
https://bugzilla.redhat.com/show_bug.cgi?id=429403#c7
I assume other people are successfully running f9 guests on f8 dom0?!
No one else having this issue?
thanks.
-matt
15 years
Long boot time (hwclock problem)
by Guillaume
Hi all,
A new problem for me. Since I was able to run guests with Xen, I'm
stuck with a time synchronization error each time system boot and
stop.
each time theses events occur, the VM seem to stop running (nothing is
displayed on screen) and after 5-10 minutes, normal `init` go on and
the
system work fine. After some search, I saw that's the problem comes
from `hwclock`. When i run it manually it display this error :
hwclock from util-linux-ng 2.13
hwclock: Open of /dev/rtc failed, errno=19: No such device. <<<<<
Using direct I/O instructions to ISA clock.
Last drift adjustment done at 1423924190 seconds after 1969
Last calibration done at 1423924190 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
I delete & recreate /dev/rtc but it does not solve the problem.
Maybe this problem was discussed before on this list but i was unable
to find any search tools on fedora/redhat website and manually search
against the subject for the 6 last month did not return me any good
answer.
So, maybe a quick solution about this veeeerrrryyyy long boot time exist.
Thanks for your help.
--
Guillaume
15 years
virt-manager 0.6.0 under CentOS 5.2 (64-bit) gives Python syntax error (invalid syntax) with domain.py, line 669
by pekka.panula＠netservant.fi
Hi
I updated virt-manager 0.6.0 and python-virtinst 0.400.0 and when i am
trying to start virt-manager i am getting Python syntax error:
--------------------8<--------------
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 346, in ?
main()
File "/usr/share/virt-manager/virt-manager.py", line 287, in main
from virtManager.engine import vmmEngine
File "/usr/share/virt-manager/virtManager/engine.py", line 31, in ?
from virtManager.connection import vmmConnection
File "/usr/share/virt-manager/virtManager/connection.py", line 36, in ?
from virtManager.domain import vmmDomain
File "/usr/share/virt-manager/virtManager/domain.py", line 669
finally:
^
SyntaxError: invalid syntax
--------------------8<--------------
CentOS using default python (RPM = python-2.4.3-21.el5):
Python 2.4.3 (#1, May 24 2008, 13:57:05)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2
My python skills are somewhat non-existent so can anyone give any help how
to fix this?
Terveisin/Regards,
Pekka Panula, Net Servant Oy
15 years
problem with virtual interface in DomU
by Guillaume
hi,
I finally achieve a goal to start a para-VM with xen. But i still experience
problem with networking inside the vm (domU).
There are no network interface shown. Maybe kernel module is not loaded for
the emulated NIC.
In domU i'm only able to see loopback interface. But, in dom0 i can see all
bridge interface and networking is OK.
Can someone help me ?
thanks.
--
Guillaume
15 years
Re: [Fedora-xen] problem with virtual interface in DomU
by Guillaume
>> It is not an HVM "build" so, i tought virtualization extensions are
>> useless ? And i don't have intel-VT on my system.
>
> That may be the entire problem.
> My understanding is that the paravirtualized kernel needs those extensions
> so that the supervisor calls do not have to go through the hypervisor.
For me it wasn't =) !
For my knowledge, HVM extension was needed by xen only for
fully-virtualized OS. (like Microsoft OS and other closed source OS ;
because no modification can't be made to their kernel to make them
aware of "xen".). But maybe i'm wrong !
And if you're right, it will explain why networking don't work (and
will never on my system)
--> but keep in mind that xen exist a "long time" before hvm
extension do. And I thought that other people made networking works in
their xen VM. So, I tought that i can get rid of this problem without
hvm set on.
Someone can light me more about it ?
thanks
--
Guillaume
15 years
Re: [Fedora-xen] problem with virtual interface in DomU
by Guillaume
2008/9/15 lamont cranston <l.cranston(a)gmail.com>
>
> 1) verify that the virtualization extensions are turned on in the BIOS (in my case, a HP prolient server, the selection was actually named "virtualization")
It is not an HVM "build" so, i tought virtualization extensions are
useless ? And i don't have intel-VT on my system.
> 2) when you get to the end of your install of the guest OS, you should have the option to "share" the network device
I did not use any wizard to create the vm (i made a copy of an
actual system to an image file, and create the "xm" config file)
> 3) easiest way to verify the guest IP is to ask the guest - you can reason it out from the host ifconfig, but just asking the guest is a lot simplier and just "feels" right :)
I'm not so good in English, what do you mean ? :-D
--
Guillaume
15 years
