System is default Suse 10.1 install with Xen 3.0.2 on Athlon 64 X2 AM2
soket.
Started the suse img from Live CD full virtualization. Supposed to have
output on screen, have nothing.
xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1739 2 r----- 281.0
suse 1 256 1 -b---- 0.0
XM dmesg
Xen version 3.0.2_09763-0.8 (abuild@suse.de) (gcc version 4.1.0 (SUSE
Linux)) Fri Oct 6 16:00:18 UTC 2006
Latest ChangeSet: 09763
(XEN) Command line: /boot/xen.gz
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007ffd0000 (usable)
(XEN) 000000007ffd0000 - 000000007ffde000 (ACPI data)
(XEN) 000000007ffde000 - 0000000080000000 (ACPI NVS)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fee00000 - 00000000fef00000 (reserved)
(XEN) 00000000ff780000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096572kB)
(XEN) Xen heap: 14MB (14528kB)
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 ACPIAM ) @
0x00000000000fa950
(XEN) ACPI: RSDT (v001 A M I OEMRSDT 0x06000602 MSFT 0x00000097) @
0x000000007ffd0000
(XEN) ACPI: FADT (v002 A M I OEMFACP 0x06000602 MSFT 0x00000097) @
0x000000007ffd0200
(XEN) ACPI: MADT (v001 A M I OEMAPIC 0x06000602 MSFT 0x00000097) @
0x000000007ffd0390
(XEN) ACPI: MCFG (v001 A M I OEMMCFG 0x06000602 MSFT 0x00000097) @
0x000000007ffd0400
(XEN) ACPI: OEMB (v001 A M I AMI_OEM 0x06000602 MSFT 0x00000097) @
0x000000007ffde040
(XEN) ACPI: DSDT (v001 1ADGH 1ADGH000 0x00000000 INTL 0x02002026) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:11 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:11 APIC version 16
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) ACPI: IRQ14 used by override.
(XEN) ACPI: IRQ15 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2000.059 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU 0(2) -> Core 0
(XEN) AMD SVM Extension is enabled for cpu 0.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU1: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU 1(2) -> Core 1
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD SVM Extension is enabled for cpu 1.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ... failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... failed.
(XEN) ...trying to set up timer as ExtINT IRQ...spurious 8259A
interrupt: IRQ7.
(XEN) works.
(XEN) checking TSC synchronization across 2 CPUs:
(XEN) CPU#0 had 28 usecs TSC skew, fixed it up.
(XEN) CPU#1 had -28 usecs TSC skew, fixed it up.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000000f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000003000000->0000000004000000 (477772 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff80464108
(XEN) Init. ramdisk: ffffffff80465000->ffffffff80a92600
(XEN) Phys-Mach map: ffffffff80a93000->ffffffff80e40260
(XEN) Start info: ffffffff80e41000->ffffffff80e42000
(XEN) Page tables: ffffffff80e42000->ffffffff80e4d000
(XEN) Boot stack: ffffffff80e4d000->ffffffff80e4e000
(XEN) TOTAL: ffffffff80000000->ffffffff81000000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x62d600, start at 0xffffffff80465000
(XEN) Scrubbing Free RAM: .....................done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
Art
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 31 October 2006 14:47 > To: xen-users@lists.xensource.com > Subject: [Xen-users] What does this mean? > > System is default Suse 10.1 install with Xen 3.0.2 on Athlon 64 X2 AM2 > soket. > > Started the suse img from Live CD full virtualization. > Supposed to have > output on screen, have nothing. > > xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 1739 2 r----- 281.0 > suse 1 256 1 -b---- 0.0 >The logs you showed doesn''t tell much about what happened to the DomU (suse)... It''s blocked and at 0 CPU time, so it''s most likely that the qemu-dm or some component like that is not working right - check /var/log/xen/qemu-dm<pid>.log (use "ls -ltr /var/log/xen/qemu*" to find the latest one... -- Mats _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 31 October 2006 14:47 > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] What does this mean? > > > > System is default Suse 10.1 install with Xen 3.0.2 on Athlon 64 X2 AM2 > > soket. > > > > Started the suse img from Live CD full virtualization. > > Supposed to have > > output on screen, have nothing. > > > > xm list > > Name ID Mem(MiB) VCPUs State Time(s) > > Domain-0 0 1739 2 r----- 281.0 > > suse 1 256 1 -b---- 0.0 > > > The logs you showed doesn''t tell much about what happened to the DomU > (suse)... > > It''s blocked and at 0 CPU time, so it''s most likely that the qemu-dm or > some component like that is not working right - check > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr /var/log/xen/qemu*" to find > the latest one... > > -- > Mats >Comes back with ls -ltr /var/log/xen/qemu* /bin/ls: /var/log/xen/qemu*: No such file or directory Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 31 October 2006 18:33 > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] What does this mean? > > On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote: > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > Of Art Fore > > > Sent: 31 October 2006 14:47 > > > To: xen-users@lists.xensource.com > > > Subject: [Xen-users] What does this mean? > > > > > > System is default Suse 10.1 install with Xen 3.0.2 on > Athlon 64 X2 AM2 > > > soket. > > > > > > Started the suse img from Live CD full virtualization. > > > Supposed to have > > > output on screen, have nothing. > > > > > > xm list > > > Name ID Mem(MiB) VCPUs State Time(s) > > > Domain-0 0 1739 2 r----- 281.0 > > > suse 1 256 1 -b---- 0.0 > > > > > The logs you showed doesn''t tell much about what happened > to the DomU > > (suse)... > > > > It''s blocked and at 0 CPU time, so it''s most likely that > the qemu-dm or > > some component like that is not working right - check > > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr > /var/log/xen/qemu*" to find > > the latest one... > > > > -- > > Mats > > > Comes back with > ls -ltr /var/log/xen/qemu* > /bin/ls: /var/log/xen/qemu*: No such file or directoryIs this a HVM or PV domain? If it''s HVM, then I would definitely expect a qemu-dm<pid>.log file. If it''s a PV domain, then I don''t expect there to be one - since I almost always work on HVM domains, I didn''t even consider that it may NOT be. -- Mats> > Art > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-31 at 19:34 +0100, Petersson, Mats wrote:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 31 October 2006 18:33 > > To: xen-users@lists.xensource.com > > Subject: RE: [Xen-users] What does this mean? > > > > On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote: > > > > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > Of Art Fore > > > > Sent: 31 October 2006 14:47 > > > > To: xen-users@lists.xensource.com > > > > Subject: [Xen-users] What does this mean? > > > > > > > > System is default Suse 10.1 install with Xen 3.0.2 on > > Athlon 64 X2 AM2 > > > > soket. > > > > > > > > Started the suse img from Live CD full virtualization. > > > > Supposed to have > > > > output on screen, have nothing. > > > > > > > > xm list > > > > Name ID Mem(MiB) VCPUs State Time(s) > > > > Domain-0 0 1739 2 r----- 281.0 > > > > suse 1 256 1 -b---- 0.0 > > > > > > > The logs you showed doesn''t tell much about what happened > > to the DomU > > > (suse)... > > > > > > It''s blocked and at 0 CPU time, so it''s most likely that > > the qemu-dm or > > > some component like that is not working right - check > > > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr > > /var/log/xen/qemu*" to find > > > the latest one... > > > > > > -- > > > Mats > > > > > Comes back with > > ls -ltr /var/log/xen/qemu* > > /bin/ls: /var/log/xen/qemu*: No such file or directory > > Is this a HVM or PV domain? > > If it''s HVM, then I would definitely expect a qemu-dm<pid>.log file. If > it''s a PV domain, then I don''t expect there to be one - since I almost > always work on HVM domains, I didn''t even consider that it may NOT be. > > -- > MatsIt is an HVM domain. Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 31 October 2006 18:47 > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] What does this mean? > > On Tue, 2006-10-31 at 19:34 +0100, Petersson, Mats wrote: > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > Of Art Fore > > > Sent: 31 October 2006 18:33 > > > To: xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] What does this mean? > > > > > > On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote: > > > > > > > > > -----Original Message----- > > > > > From: xen-users-bounces@lists.xensource.com > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > Of Art Fore > > > > > Sent: 31 October 2006 14:47 > > > > > To: xen-users@lists.xensource.com > > > > > Subject: [Xen-users] What does this mean? > > > > > > > > > > System is default Suse 10.1 install with Xen 3.0.2 on > > > Athlon 64 X2 AM2 > > > > > soket. > > > > > > > > > > Started the suse img from Live CD full virtualization. > > > > > Supposed to have > > > > > output on screen, have nothing. > > > > > > > > > > xm list > > > > > Name ID Mem(MiB) VCPUs > State Time(s) > > > > > Domain-0 0 1739 2 > r----- 281.0 > > > > > suse 1 256 1 > -b---- 0.0 > > > > > > > > > The logs you showed doesn''t tell much about what happened > > > to the DomU > > > > (suse)... > > > > > > > > It''s blocked and at 0 CPU time, so it''s most likely that > > > the qemu-dm or > > > > some component like that is not working right - check > > > > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr > > > /var/log/xen/qemu*" to find > > > > the latest one... > > > > > > > > -- > > > > Mats > > > > > > > Comes back with > > > ls -ltr /var/log/xen/qemu* > > > /bin/ls: /var/log/xen/qemu*: No such file or directory > > > > Is this a HVM or PV domain? > > > > If it''s HVM, then I would definitely expect a > qemu-dm<pid>.log file. If > > it''s a PV domain, then I don''t expect there to be one - > since I almost > > always work on HVM domains, I didn''t even consider that it > may NOT be. > > > > -- > > Mats > It is an HVM domain.Ok, so you probably have something not working right in the startup of the HVM domain... Is there anything about hvmloader or qemu in /var/log/xen*.log ? -- Mats> > Art > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-31 at 19:55 +0100, Petersson, Mats wrote:> > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 31 October 2006 18:47 > > To: xen-users@lists.xensource.com > > Subject: RE: [Xen-users] What does this mean? > > > > On Tue, 2006-10-31 at 19:34 +0100, Petersson, Mats wrote: > > > > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > Of Art Fore > > > > Sent: 31 October 2006 18:33 > > > > To: xen-users@lists.xensource.com > > > > Subject: RE: [Xen-users] What does this mean? > > > > > > > > On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote: > > > > > > > > > > > -----Original Message----- > > > > > > From: xen-users-bounces@lists.xensource.com > > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > > Of Art Fore > > > > > > Sent: 31 October 2006 14:47 > > > > > > To: xen-users@lists.xensource.com > > > > > > Subject: [Xen-users] What does this mean? > > > > > > > > > > > > System is default Suse 10.1 install with Xen 3.0.2 on > > > > Athlon 64 X2 AM2 > > > > > > soket. > > > > > > > > > > > > Started the suse img from Live CD full virtualization. > > > > > > Supposed to have > > > > > > output on screen, have nothing. > > > > > > > > > > > > xm list > > > > > > Name ID Mem(MiB) VCPUs > > State Time(s) > > > > > > Domain-0 0 1739 2 > > r----- 281.0 > > > > > > suse 1 256 1 > > -b---- 0.0 > > > > > > > > > > > The logs you showed doesn''t tell much about what happened > > > > to the DomU > > > > > (suse)... > > > > > > > > > > It''s blocked and at 0 CPU time, so it''s most likely that > > > > the qemu-dm or > > > > > some component like that is not working right - check > > > > > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr > > > > /var/log/xen/qemu*" to find > > > > > the latest one... > > > > > > > > > > -- > > > > > Mats > > > > > > > > > Comes back with > > > > ls -ltr /var/log/xen/qemu* > > > > /bin/ls: /var/log/xen/qemu*: No such file or directory > > > > > > Is this a HVM or PV domain? > > > > > > If it''s HVM, then I would definitely expect a > > qemu-dm<pid>.log file. If > > > it''s a PV domain, then I don''t expect there to be one - > > since I almost > > > always work on HVM domains, I didn''t even consider that it > > may NOT be. > > > > > > -- > > > Mats > > It is an HVM domain. > > Ok, so you probably have something not working right in the startup of > the HVM domain... Is there anything about hvmloader or qemu in > /var/log/xen*.log ? > > -- > Mats > > > > Arthere is from the /var/log/xend log from the last reboot. [2006-11-01 03:04:44 xend] INFO (SrvDaemon:278) Xend Daemon started [2006-11-01 03:04:44 xend] INFO (SrvDaemon:282) Xend changeset: 09763. [2006-11-01 03:04:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:202) XendDomainInfo.recreate({''paused'': 0, ''cpu_time'': 22074226301L, ''ssidref'': 0, ''handle'': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], ''shutdown_reason'': 0, ''dying'': 0, ''dom'': 0, ''mem_kb'': 1927472, ''maxmem_kb'': 17179869180, ''max_vcpu_id'': 1, ''crashed'': 0, ''running'': 1, ''shutdown'': 0, ''online_vcpus'': 2, ''blocked'': 0}) [2006-11-01 03:04:44 xend.XendDomainInfo] INFO (XendDomainInfo:214) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-11-01 03:04:44 xend.XendDomainInfo] WARNING (XendDomainInfo:236) No vm path in store for existing domain 0 [2006-11-01 03:04:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:675) Storing VM details: {''ssidref'': ''0'', ''uuid'': ''00000000-0000-0000-0000-000000000000'', ''on_reboot'': ''restart'', ''on_poweroff'': ''destroy'', ''name'': ''Domain-0'', ''vcpus'': ''2'', ''vcpu_avail'': ''3'', ''memory'': ''1883'', ''on_crash'': ''restart'', ''maxmem'': ''1883''} [2006-11-01 03:04:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:700) Storing domain details: {''cpu/0/availability'': ''online'', ''memory/target'': ''1928192'', ''cpu/1/availability'': ''online'', ''name'': ''Domain-0'', ''console/limit'': ''1048576'', ''vm'': ''/vm/00000000-0000-0000-0000-000000000000'', ''domid'': ''0''} [2006-11-01 03:04:44 xend] DEBUG (XendDomain:152) number of vcpus to use is 0 [2006-11-01 03:04:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:881) XendDomainInfo.handleShutdownWatch [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:180) XendDomainInfo.create([''vm'', [''name'', ''suse''], [''memory'', 256], [''on_poweroff'', ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], [''vcpus'', 1], [''image'', [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', 1], [''boot'', ''c''], [''sdl'', 1], [''xauthority'', ''//.Xauthority'']]], [''device'', [''vbd'', [''uname'', ''file:/windows/opensuse/suse.img''], [''dev'', ''ioemu:hdd''], [''mode'', ''w'']]], [''device'', [''vif'', [''mac'', ''00:16:3e:2b:f6:6d''], [''type'', ''ioemu'']]]]) [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:286) parseConfig: config is [''vm'', [''name'', ''suse''], [''memory'', 256], [''on_poweroff'', ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], [''vcpus'', 1], [''image'', [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', 1], [''boot'', ''c''], [''sdl'', 1], [''xauthority'', ''//.Xauthority'']]], [''device'', [''vbd'', [''uname'', ''file:/windows/opensuse/suse.img''], [''dev'', ''ioemu:hdd''], [''mode'', ''w'']]], [''device'', [''vif'', [''mac'', ''00:16:3e:2b:f6:6d''], [''type'', ''ioemu'']]]] [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:382) parseConfig: result is {''ssidref'': None, ''uuid'': None, ''on_crash'': ''restart'', ''on_reboot'': ''restart'', ''localtime'': None, ''image'': [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', 1], [''boot'', ''c''], [''sdl'', 1], [''xauthority'', ''//.Xauthority'']], ''on_poweroff'': ''destroy'', ''cpus'': None, ''name'': ''suse'', ''backend'': [], ''cpu'': None, ''vcpus'': 1, ''cpu_weight'': None, ''vcpu_avail'': None, ''memory'': 256, ''device'': [(''vbd'', [''vbd'', [''uname'', ''file:/windows/opensuse/suse.img''], [''dev'', ''ioemu:hdd''], [''mode'', ''w'']]), (''vif'', [''vif'', [''mac'', ''00:16:3e:2b:f6:6d''], [''type'', ''ioemu'']])], ''bootloader'': None, ''root'': None, ''bootentry'': None, ''maxmem'': None} [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:1189) XendDomainInfo.construct: None 0 [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:1221) XendDomainInfo.initDomain: 1 1.0 [2006-11-01 03:04:49 xend] DEBUG (image:269) args: cdrom, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: boot, val: c [2006-11-01 03:04:49 xend] DEBUG (image:269) args: fda, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: fdb, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: nic-ne2000, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: enable-audio, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: localtime, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: serial, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: std-vga, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: isa, val: None [2006-11-01 03:04:49 xend] DEBUG (image:269) args: vcpus, val: 1 [2006-11-01 03:04:49 xend] DEBUG (balloon:143) Balloon: 127776 KiB free; 0 to scrub; need 275048; retries: 20. [2006-11-01 03:04:49 xend] DEBUG (balloon:158) Balloon: setting dom0 target to 1739 MiB. [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:970) Setting memory target of domain Domain-0 (0) to 1739 MiB. [2006-11-01 03:04:49 xend] DEBUG (balloon:137) Balloon: 275232 KiB free; need 275048; done. [2006-11-01 03:04:49 xend] INFO (image:136) buildDomain os=hvm dom=1 vcpus=1 [2006-11-01 03:04:49 xend] DEBUG (image:227) dom = 1 [2006-11-01 03:04:49 xend] DEBUG (image:228) image = /usr/lib/xen/boot/hvmloader [2006-11-01 03:04:49 xend] DEBUG (image:229) store_evtchn = 1 [2006-11-01 03:04:49 xend] DEBUG (image:230) memsize = 256 [2006-11-01 03:04:49 xend] DEBUG (image:231) vcpus = 1 [2006-11-01 03:04:49 xend] DEBUG (image:232) pae = 0 [2006-11-01 03:04:49 xend] DEBUG (image:233) acpi = 0 [2006-11-01 03:04:49 xend] DEBUG (image:234) apic = 0 [2006-11-01 03:04:49 xend] DEBUG (image:404) hvm shutdown watch registered [2006-11-01 03:04:49 xend] DEBUG (blkif:24) exception looking up device number for hdd: [Errno 2] No such file or directory: ''/dev/hdd'' [2006-11-01 03:04:49 xend] DEBUG (DevController:103) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vbd/1/5696''} to /local/domain/1/device/vbd/5696. [2006-11-01 03:04:49 xend] DEBUG (DevController:105) DevController: writing {''domain'': ''suse'', ''frontend'': ''/local/domain/1/device/vbd/5696'', ''dev'': ''ioemu:hdd'', ''state'': ''1'', ''params'': ''/windows/opensuse/suse.img'', ''mode'': ''w'', ''frontend-id'': ''1'', ''type'': ''file''} to /local/domain/0/backend/vbd/1/5696. [2006-11-01 03:04:49 xend] DEBUG (DevController:103) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vif/1/0''} to /local/domain/1/device/vif/0. [2006-11-01 03:04:49 xend] DEBUG (DevController:105) DevController: writing {''domain'': ''suse'', ''handle'': ''0'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': ''/local/domain/1/device/vif/0'', ''mac'': ''00:16:3e:2b:f6:6d'', ''frontend-id'': ''1'', ''type'': ''ioemu''} to /local/domain/0/backend/vif/1/0. [2006-11-01 03:04:49 xend] INFO (image:358) spawning device models: /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'', ''-d'', ''1'', ''-m'', ''256'', ''-boot'', ''c'', ''-vcpus'', ''1'', ''-domain-name'', ''suse'', ''-hdd'', ''/windows/opensuse/suse.img'', ''-macaddr'', ''00:16:3e:2b:f6:6d'', ''-bridge'', ''xenbr0'', ''-nics'', ''1''] [2006-11-01 03:04:49 xend] INFO (image:360) device model pid: 5406 [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:675) Storing VM details: {''ssidref'': ''0'', ''uuid'': ''ebfc9a86-b293-9995-bda2-a961b4a26ed0'', ''on_reboot'': ''restart'', ''start_time'': ''1162321489.98'', ''on_poweroff'': ''destroy'', ''name'': ''suse'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''256'', ''on_crash'': ''restart'', ''image'': ''(hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm) (vcpus 1) (boot c) (sdl 1) (xauthority //.Xauthority))'', ''maxmem'': ''256''} [2006-11-01 03:04:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:700) Storing domain details: {''console/port'': ''2'', ''name'': ''suse'', ''console/limit'': ''1048576'', ''vm'': ''/vm/ebfc9a86-b293-9995-bda2-a961b4a26ed0'', ''domid'': ''1'', ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', ''store/ring-ref'': ''380105'', ''store/port'': ''1''} [2006-11-01 03:04:50 xend] DEBUG (image:427) hvm_shutdown fired, shutdown reason=None [2006-11-01 03:04:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:881) XendDomainInfo.handleShutdownWatch [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices vif. [2006-11-01 03:04:50 xend] DEBUG (DevController:138) Waiting for 0. [2006-11-01 03:04:50 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-11-01 03:04:50 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-11-01 03:04:50 xend] DEBUG (DevController:417) hotplugStatusCallback 1. [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices usb. [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices vbd. [2006-11-01 03:04:50 xend] DEBUG (DevController:138) Waiting for 5696. [2006-11-01 03:04:50 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vbd/1/5696/hotplug-status. [2006-11-01 03:04:50 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vbd/1/5696/hotplug-status. [2006-11-01 03:04:50 xend] DEBUG (DevController:417) hotplugStatusCallback 1. [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices irq. [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices pci. [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices ioports. [2006-11-01 03:04:50 xend] DEBUG (DevController:132) Waiting for devices vtpm. [2006-11-01 03:04:50 xend] INFO (XendDomain:363) Domain suse (1) unpaused. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 31 October 2006 19:15 > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] What does this mean? > > On Tue, 2006-10-31 at 19:55 +0100, Petersson, Mats wrote: > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > Of Art Fore > > > Sent: 31 October 2006 18:47 > > > To: xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] What does this mean? > > > > > > On Tue, 2006-10-31 at 19:34 +0100, Petersson, Mats wrote: > > > > > > > > > -----Original Message----- > > > > > From: xen-users-bounces@lists.xensource.com > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > Of Art Fore > > > > > Sent: 31 October 2006 18:33 > > > > > To: xen-users@lists.xensource.com > > > > > Subject: RE: [Xen-users] What does this mean? > > > > > > > > > > On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote: > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: xen-users-bounces@lists.xensource.com > > > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > > > Of Art Fore > > > > > > > Sent: 31 October 2006 14:47 > > > > > > > To: xen-users@lists.xensource.com > > > > > > > Subject: [Xen-users] What does this mean? > > > > > > > > > > > > > > System is default Suse 10.1 install with Xen 3.0.2 on > > > > > Athlon 64 X2 AM2 > > > > > > > soket. > > > > > > > > > > > > > > Started the suse img from Live CD full virtualization. > > > > > > > Supposed to have > > > > > > > output on screen, have nothing. > > > > > > > > > > > > > > xm list > > > > > > > Name ID Mem(MiB) VCPUs > > > State Time(s) > > > > > > > Domain-0 0 1739 2 > > > r----- 281.0 > > > > > > > suse 1 256 1 > > > -b---- 0.0 > > > > > > > > > > > > > The logs you showed doesn''t tell much about what happened > > > > > to the DomU > > > > > > (suse)... > > > > > > > > > > > > It''s blocked and at 0 CPU time, so it''s most likely that > > > > > the qemu-dm or > > > > > > some component like that is not working right - check > > > > > > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr > > > > > /var/log/xen/qemu*" to find > > > > > > the latest one... > > > > > > > > > > > > -- > > > > > > Mats > > > > > > > > > > > Comes back with > > > > > ls -ltr /var/log/xen/qemu* > > > > > /bin/ls: /var/log/xen/qemu*: No such file or directory > > > > > > > > Is this a HVM or PV domain? > > > > > > > > If it''s HVM, then I would definitely expect a > > > qemu-dm<pid>.log file. If > > > > it''s a PV domain, then I don''t expect there to be one - > > > since I almost > > > > always work on HVM domains, I didn''t even consider that it > > > may NOT be. > > > > > > > > -- > > > > Mats > > > It is an HVM domain. > > > > Ok, so you probably have something not working right in the > startup of > > the HVM domain... Is there anything about hvmloader or qemu in > > /var/log/xen*.log ? > > > > -- > > Mats > > > > > > Art > here is from the /var/log/xend log from the last reboot.[snip] I can''t see anything wrong in that log-file. Anything in /var/log/xend-debug.log that may help? -- Mats> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-31 at 20:18 +0100, Petersson, Mats wrote:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 31 October 2006 19:15 > > To: xen-users@lists.xensource.com > > Subject: RE: [Xen-users] What does this mean? > > > > On Tue, 2006-10-31 at 19:55 +0100, Petersson, Mats wrote: > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > Of Art Fore > > > > Sent: 31 October 2006 18:47 > > > > To: xen-users@lists.xensource.com > > > > Subject: RE: [Xen-users] What does this mean? > > > > > > > > On Tue, 2006-10-31 at 19:34 +0100, Petersson, Mats wrote: > > > > > > > > > > > -----Original Message----- > > > > > > From: xen-users-bounces@lists.xensource.com > > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > > Of Art Fore > > > > > > Sent: 31 October 2006 18:33 > > > > > > To: xen-users@lists.xensource.com > > > > > > Subject: RE: [Xen-users] What does this mean? > > > > > > > > > > > > On Tue, 2006-10-31 at 15:50 +0100, Petersson, Mats wrote: > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: xen-users-bounces@lists.xensource.com > > > > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > > > > Of Art Fore > > > > > > > > Sent: 31 October 2006 14:47 > > > > > > > > To: xen-users@lists.xensource.com > > > > > > > > Subject: [Xen-users] What does this mean? > > > > > > > > > > > > > > > > System is default Suse 10.1 install with Xen 3.0.2 on > > > > > > Athlon 64 X2 AM2 > > > > > > > > soket. > > > > > > > > > > > > > > > > Started the suse img from Live CD full virtualization. > > > > > > > > Supposed to have > > > > > > > > output on screen, have nothing. > > > > > > > > > > > > > > > > xm list > > > > > > > > Name ID Mem(MiB) VCPUs > > > > State Time(s) > > > > > > > > Domain-0 0 1739 2 > > > > r----- 281.0 > > > > > > > > suse 1 256 1 > > > > -b---- 0.0 > > > > > > > > > > > > > > > The logs you showed doesn''t tell much about what happened > > > > > > to the DomU > > > > > > > (suse)... > > > > > > > > > > > > > > It''s blocked and at 0 CPU time, so it''s most likely that > > > > > > the qemu-dm or > > > > > > > some component like that is not working right - check > > > > > > > /var/log/xen/qemu-dm<pid>.log (use "ls -ltr > > > > > > /var/log/xen/qemu*" to find > > > > > > > the latest one... > > > > > > > > > > > > > > -- > > > > > > > Mats > > > > > > > > > > > > > Comes back with > > > > > > ls -ltr /var/log/xen/qemu* > > > > > > /bin/ls: /var/log/xen/qemu*: No such file or directory > > > > > > > > > > Is this a HVM or PV domain? > > > > > > > > > > If it''s HVM, then I would definitely expect a > > > > qemu-dm<pid>.log file. If > > > > > it''s a PV domain, then I don''t expect there to be one - > > > > since I almost > > > > > always work on HVM domains, I didn''t even consider that it > > > > may NOT be. > > > > > > > > > > -- > > > > > Mats > > > > It is an HVM domain. > > > > > > Ok, so you probably have something not working right in the > > startup of > > > the HVM domain... Is there anything about hvmloader or qemu in > > > /var/log/xen*.log ? > > > > > > -- > > > Mats > > > > > > > > Art > > here is from the /var/log/xend log from the last reboot. > [snip] > I can''t see anything wrong in that log-file. Anything in > /var/log/xend-debug.log that may help? > > -- > Mats > >That files is 0 bytes. Art> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users