|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1769] xl created hvm windows gets stuck after guest reboot
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1769 ------- Comment #8 from lev.v.kuznetsov@xxxxxxxxx 2011-10-07 07:38 ------- I got the same thing while installing Debian as HVM with xl create, dom0 is debian kernel 3.0 x64 with upstream xen version 4.1.1 (Debian 4.1.1-2). DomU got stuck on the reboot after install. I get the same errors trying to destroy by ID, here's list -v output: levk@tortuga:~$ sudo xl list -v Name ID Mem VCPUs State Time(s) UUID Reason-Code Domain-0 0 1820 4 r----- 31412.6 00000000-0000-0000-0000-000000000000 - isla-de-muerta 56 4091 2 -b---- 6738.1 822b9df2-eb71-11e0-b55f-0024e845eb74 - (null) 57 409 2 --psrd 82.9 400d2a0c-f0ea-11e0-bdc4-0024e845eb74 1 I can't find any way to attach so I'm pasting inline, qemu-dm-X.log: domid: 57 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Using file /dev/vg-store/davy-jones-locker in read-write mode Strip off blktap sub-type prefix to /usr/share/xen/iso/debian-6.0.2.1-netinst-amd64.iso (drv 'aio') Using file /usr/share/xen/iso/debian-6.0.2.1-netinst-amd64.iso in read-only mode Watching /local/domain/0/device-model/57/logdirty/cmd Watching /local/domain/0/device-model/57/command Watching /local/domain/57/cpu char device redirected to /dev/pts/5 qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 400d2a0c-f0ea-11e0-bdc4-0024e845eb74 xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/57/xen_extended_power_mgmt): read error medium change watch on `hdb' (index: 1): aio:/usr/share/xen/iso/debian-6.0.2.1-netinst-amd64.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. xs_read(/local/domain/57/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/57/log-throttling' medium change watch on `/local/domain/57/log-throttling' - unknown device, ignored xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. Unknown PV product 3 loaded in guest PV driver build 1 region type 1 at [c100,c120). Time offset set 4, added offset 4 reset requested in cpu_handle_ioreq. Issued domain 57 reboot medium change watch on `hdb' (index: 1): aio: medium change watch on `hdb' (index: 1): aio: xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device xen be core: xen be core: can't open gnttab device can't open gnttab device vcpu-set: watch node error. xs_read(/local/domain/57/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/57/log-throttling' medium change watch on `/local/domain/57/log-throttling' - unknown device, ignored xl-X.log: Waiting for domain davy-jones-locker (domid 57) to die [pid 27577] and this is xen-hotplug.log: RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported Cannot find device "tap10.0" /etc/xen/scripts/locking.sh: line 109: /var/run/xen-hotplug/block/owner: No such file or directory Cannot find device "tap11.0" RTNETLINK answers: Operation not supported Cannot find device "tap12.0" RTNETLINK answers: Operation not supported /etc/xen/scripts/locking.sh: line 109: /var/run/xen-hotplug/block/owner: No such file or directory xenstore-read: couldn't read path backend/vbd/12/2064/node RTNETLINK answers: Operation not supported Cannot find device "tap13.0" xenstore-read: couldn't read path backend/vbd/13/2064/node Cannot find device "vif14.0" Cannot find device "tap14.0" /etc/xen/scripts/locking.sh: line 109: /var/run/xen-hotplug/block/owner: No such file or directory RTNETLINK answers: Operation not supported Cannot find device "tap15.0" xenstore-read: couldn't read path backend/vbd/15/2064/node RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported /etc/xen/scripts/locking.sh: line 109: /var/run/xen-hotplug/block/owner: No such file or directory RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported xenstore-read: couldn't read path backend/vbd/17/5632/params xenstore-read: couldn't read path backend/vbd/17/5696/params RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported Cannot find device "tap22.0" Cannot find device "tap23.0" RTNETLINK answers: Operation not supported /etc/xen/scripts/locking.sh: line 109: /var/run/xen-hotplug/block/owner: No such file or directory RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported /etc/xen/scripts/locking.sh: line 109: /var/run/xen-hotplug/block/owner: No such file or directory RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |