11:12 p.m.
[root@potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty
-no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net
nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0 -usb
-usbdevice tablet -vnc 0.0.0.0:0
char device redirected to /dev/pts/35
unhandled vm exit: 0x9
rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx
000000000000001f
rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp
000000000003f458
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
0000000000000000
rip 000000008051ecc3 rflags 00010246
cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt 8003f000/3ff
idt 8003f400/7ff
cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
Aborted
[root@potoroo ~]#
I created the file /var/lib/xen/images/rto-test.img by installing
Windows XP to the point it reboots.
I then attached /var/lib/xen/images/rto-test.img to my Debian rescue
system, and copied /var/lib/xen/images/rto.img to it using ntfsclone.
This is the ntfsresize info on the file:
[root@potoroo ~]# ntfsresize --info /var/lib/xen/images/rto.img -f
ntfsresize v1.13.1 (libntfs 9:0:0)
Device name : /var/lib/xen/images/rto.img
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 11999994368 bytes (12000 MB)
Current device size: 60011606528 bytes (60012 MB)
ERROR: This software has detected that the disk has at least 2 bad sectors.
****************************************************************************
* WARNING: The disk has bad sector. This means physical damage on the disk *
* surface caused by deterioration, manufacturing faults or other reason. *
* The reliability of the disk may stay stable or degrade fast. We suggest *
* making a full backup urgently by running 'ntfsclone --rescue ...' then *
* run 'chkdsk /f /r' on Windows and rebooot it TWICE! Then you can resize *
* NTFS safely by additionally using the --bad-sectors option of ntfsresize.*
****************************************************************************
[root@potoroo ~]#
Note that the bad sectors are a legacy of the install to the original,
long deceased drive. I've not found a way to clear it, the system runs
ine and the bad sectors are not relevant to the problem.
This is the image I'm trying to boot:
[root@potoroo ~]# parted /var/lib/xen/images/rto-test.img print
Model: (file)
Disk /var/lib/xen/images/rto-test.img: 14.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 14.7GB 14.7GB primary ntfs boot
[root@potoroo ~]#
the MBR is fine:
[root@potoroo ~]# cat /var/lib/xen/images/rto-test.img | xxd | head -32
0000000: 33c0 8ed0 bc00 7cfb 5007 501f fcbe 1b7c 3.....|.P.P....|
0000010: bf1b 0650 57b9 e501 f3a4 cbbd be07 b104 ...PW...........
0000020: 386e 007c 0975 1383 c510 e2f4 cd18 8bf5 8n.|.u..........
0000030: 83c6 1049 7419 382c 74f6 a0b5 07b4 078b ...It.8,t.......
0000040: f0ac 3c00 74fc bb07 00b4 0ecd 10eb f288 ..<.t...........
0000050: 4e10 e846 0073 2afe 4610 807e 040b 740b N..F.s*.F..~..t.
0000060: 807e 040c 7405 a0b6 0775 d280 4602 0683 .~..t....u..F...
0000070: 4608 0683 560a 00e8 2100 7305 a0b6 07eb F...V...!.s.....
0000080: bc81 3efe 7d55 aa74 0b80 7e10 0074 c8a0 ..>.}U.t..~..t..
0000090: b707 eba9 8bfc 1e57 8bf5 cbbf 0500 8a56 .......W.......V
00000a0: 00b4 08cd 1372 238a c124 3f98 8ade 8afc .....r#..$?.....
00000b0: 43f7 e38b d186 d6b1 06d2 ee42 f7e2 3956 C..........B..9V
00000c0: 0a77 2372 0539 4608 731c b801 02bb 007c .w#r.9F.s......|
00000d0: 8b4e 028b 5600 cd13 7351 4f74 4e32 e48a .N..V...sQOtN2..
00000e0: 5600 cd13 ebe4 8a56 0060 bbaa 55b4 41cd V......V.`..U.A.
00000f0: 1372 3681 fb55 aa75 30f6 c101 742b 6160 .r6..U.u0...t+a`
0000100: 6a00 6a00 ff76 0aff 7608 6a00 6800 7c6a j.j..v..v.j.h.|j
0000110: 016a 10b4 428b f4cd 1361 6173 0e4f 740b .j..B....aas.Ot.
0000120: 32e4 8a56 00cd 13eb d661 f9c3 496e 7661 2..V.....a..Inva
0000130: 6c69 6420 7061 7274 6974 696f 6e20 7461 lid partition ta
0000140: 626c 6500 4572 726f 7220 6c6f 6164 696e ble.Error loadin
0000150: 6720 6f70 6572 6174 696e 6720 7379 7374 g operating syst
0000160: 656d 004d 6973 7369 6e67 206f 7065 7261 em.Missing opera
0000170: 7469 6e67 2073 7973 7465 6d00 0000 0000 ting system.....
0000180: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000190: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00001a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00001b0: 0000 0000 002c 4463 857a 857a 0000 8001 .....,Dc.z.z....
00001c0: 0100 07fe ffff 3f00 0000 f811 b501 0000 ......?.........
00001d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00001e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00001f0: 0000 0000 0000 0000 0000 0000 0000 55aa ..............U.
[root@potoroo ~]#
Oh, in case it matters:
[root@potoroo ~]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
stepping : 6
cpu MHz : 1596.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 3725.73
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
etc
and
[root@potoroo ~]# uname -a
Linux potoroo.demo.lan 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:36 EST
2007 x86_64 x86_64 x86_64 GNU/Linux
What is wrong, and what do I need to do to fix it?
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
12:17 a.m.
John Summerfield wrote:
What is wrong, and what do I need to do to fix it?
I rebooted to a xen kernel, created a .hvm configuration file with vim
and it's booted and currently doing a filesystem check (as expected).
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
3:37 a.m.
John Summerfield wrote:
[root@potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty
-no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net
nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0
-usb -usbdevice tablet -vnc 0.0.0.0:0
char device redirected to /dev/pts/35
unhandled vm exit: 0x9
rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx
000000000000001f
rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp
000000000003f458
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
0000000000000000
rip 000000008051ecc3 rflags 00010246
cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt 8003f000/3ff
idt 8003f400/7ff
cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
Aborted
[root@potoroo ~]#
I created the file /var/lib/xen/images/rto-test.img by installing
Windows XP to the point it reboots.
Did you also install it with -no-acpi? What happens if you drop that
option?
--
error compiling committee.c: too many arguments to function
6:30 p.m.
Avi Kivity wrote:
John Summerfield wrote:
> [root@potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty
> -no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net
> nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0
> -usb -usbdevice tablet -vnc 0.0.0.0:0
> char device redirected to /dev/pts/35
> unhandled vm exit: 0x9
> rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx
> 000000000000001f
> rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp
> 000000000003f458
> r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11
> 0000000000000000
> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
> 0000000000000000
> rip 000000008051ecc3 rflags 00010246
> cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
> ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
> es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
> tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
> ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> gdt 8003f000/3ff
> idt 8003f400/7ff
> cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
> Aborted
> [root@potoroo ~]#
>
>
> I created the file /var/lib/xen/images/rto-test.img by installing
> Windows XP to the point it reboots.
>
Did you also install it with -no-acpi? What happens if you drop that
option?
That commandline is copied from virt-manager's log, where it was
accompanied by similar, maybe exactly the same, registers dump and the
same error.
What I'm seeking is information about what the error means; without it
users have almost no chance of fixing the problem themselves.
Without "-no-acpi" it runs at 105% or so CPU. vncviewer::5900 connects
but does not open a window.
[root@potoroo ~]# lsof -i | grep -E '*:5[0-9]{3}\>'
xinetd 2180 root 5u IPv6 7547 TCP *:5902 (LISTEN)
Xvnc 2456 root 5u IPv4 8354 TCP *:5966 (LISTEN)
Xvnc 2456 root 6u IPv4 8355 TCP *:5866 (LISTEN)
Xvnc 2456 root 48u IPv4 22337 TCP
localhost.localdomain:5966->localhost.localdomain:47032 (ESTABLISHED)
Xvnc 2500 summer 5u IPv4 8473 TCP *:5903 (LISTEN)
Xvnc 2500 summer 6u IPv4 8474 TCP *:5803 (LISTEN)
vncviewer 5533 summer 4u IPv4 22336 TCP
localhost.localdomain:47032->localhost.localdomain:5966 (ESTABLISHED)
qemu-kvm 5604 root 8u IPv4 22589 TCP *:5900 (LISTEN)
vncviewer 5615 root 4u IPv4 22608 TCP
localhost.localdomain:34608->localhost.localdomain:5900 (ESTABLISHED)
[root@potoroo ~]#
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
9:44 a.m.
John Summerfield wrote:
Avi Kivity wrote:
> John Summerfield wrote:
>> [root@potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty
>> -no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net
>> nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0
>> -usb -usbdevice tablet -vnc 0.0.0.0:0
>> char device redirected to /dev/pts/35
>> unhandled vm exit: 0x9
>> rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx
>> 000000000000001f
>> rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp
>> 000000000003f458
>> r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11
>> 0000000000000000
>> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
>> 0000000000000000
>> rip 000000008051ecc3 rflags 00010246
>> cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
>> ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
>> es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
>> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
>> tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
>> ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
>> gdt 8003f000/3ff
>> idt 8003f400/7ff
>> cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
>> Aborted
>> [root@potoroo ~]#
>>
>>
>> I created the file /var/lib/xen/images/rto-test.img by installing
>> Windows XP to the point it reboots.
>>
>
> Did you also install it with -no-acpi? What happens if you drop that
> option?
>
That commandline is copied from virt-manager's log, where it was
accompanied by similar, maybe exactly the same, registers dump and the
same error.
What I'm seeking is information about what the error means; without it
users have almost no chance of fixing the problem themselves.
Well, the guest executed a hardware context switch. Windows does this
sometimes on the way to a blue screen as a means to get into a known
state. VT (and SVM) don't support hardware context switching, hence the
dump.
Without "-no-acpi" it runs at 105% or so CPU.
vncviewer::5900 connects
but does not open a window.
[root@potoroo ~]# lsof -i | grep -E '*:5[0-9]{3}\>'
xinetd 2180 root 5u IPv6 7547 TCP *:5902 (LISTEN)
Xvnc 2456 root 5u IPv4 8354 TCP *:5966 (LISTEN)
Xvnc 2456 root 6u IPv4 8355 TCP *:5866 (LISTEN)
Xvnc 2456 root 48u IPv4 22337 TCP
localhost.localdomain:5966->localhost.localdomain:47032 (ESTABLISHED)
Xvnc 2500 summer 5u IPv4 8473 TCP *:5903 (LISTEN)
Xvnc 2500 summer 6u IPv4 8474 TCP *:5803 (LISTEN)
vncviewer 5533 summer 4u IPv4 22336 TCP
localhost.localdomain:47032->localhost.localdomain:5966 (ESTABLISHED)
qemu-kvm 5604 root 8u IPv4 22589 TCP *:5900 (LISTEN)
vncviewer 5615 root 4u IPv4 22608 TCP
localhost.localdomain:34608->localhost.localdomain:5900 (ESTABLISHED)
[root@potoroo ~]#
Can you try with upstream kvm (from kvm.qumranet.com)? Though I doubt
it's a problem with F8's kvm as XP is such a widely used guest.
--
error compiling committee.c: too many arguments to function
5948
days inactive
5954
days old
4 comments
2 participants
participants (2)
-
Avi Kivity -
John Summerfield