thr3ads.net - Xen users - [Xen-users] SVM not detected on Opteron 1220 [Jul 2009]

If this information is useful, please help other people find it:
Share via:

Brian P. Martin

2009-Jul-27 18:14 UTC

[Xen-users] SVM not detected on Opteron 1220

I have SuperMicro mainboard, H8SMi-2 rev 2.01, with a dual core Opteron 1220
processor.  I''ve verified that the BIOS had "Secure Virtual
Machine"
enabled.  This appears to be the only virtualization option in the BIOS.
I''m running xen 3.3.1 and kernel-xen-base 2.6.27.  When I boot up the
"svm"
flag doesn''t appear in the /proc/cpuinfo flags area (full cpuinfo shown
at
bottom).  In essence, it seems that the BIOS says virtualization is enabled,
but Linux says it isn''t.

I tried updating the BIOS to the latest version, but that didn''t change
anything. 
Does anyone have any recommendations as to how to proceed?  Any advice would
be greatly appreciated.

                                         -Brian M.

/proc/cpuinfo:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 67
model name      : Dual-Core AMD Opteron(tm) Processor 1220
stepping        : 3
cpu MHz         : 2814.456
cache size      : 1024 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx fxsr
sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl pni
cx16 lahf_lm cmp_legacy extapic cr8_legacy
bogomips        : 5630.48
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 67
model name      : Dual-Core AMD Opteron(tm) Processor 1220
stepping        : 3
cpu MHz         : 2814.456
cache size      : 1024 KB
physical id     : 0
siblings        : 1
core id         : 1
cpu cores       : 1
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx fxsr
sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl pni
cx16 lahf_lm cmp_legacy extapic cr8_legacy
bogomips        : 5630.48
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

<djmagee@mageenet.net>

2009-Jul-27 20:17 UTC

head link

RE: [Xen-users] SVM not detected on Opteron 1220

I believe this is normal (though I don''t have any AMD hardware, it
should be the same as vmx flag on intel).  Xen masks certain bits in the
cpu information, and Dom0 does not have direct access to the physical
CPUs, only the virtual CPUs assigned by the hypervisor.

To verify you have svm enabled, you will want to look at the output of
"xm info", specifically the line that starts "xen_caps".  If
you have
entries there that start with "hvm" then your hardware supports
virtualization.

Doug Magee

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Brian P.
Martin
Sent: Monday, July 27, 2009 2:14 PM
To: xen-users@lists.xensource.com
Subject: [Xen-users] SVM not detected on Opteron 1220

I have SuperMicro mainboard, H8SMi-2 rev 2.01, with a dual core Opteron
1220
processor.  I''ve verified that the BIOS had "Secure Virtual
Machine"
enabled.  This appears to be the only virtualization option in the BIOS.
I''m running xen 3.3.1 and kernel-xen-base 2.6.27.  When I boot up the
"svm"
flag doesn''t appear in the /proc/cpuinfo flags area (full cpuinfo shown
at
bottom).  In essence, it seems that the BIOS says virtualization is
enabled,
but Linux says it isn''t.

I tried updating the BIOS to the latest version, but that didn''t change
anything. 
Does anyone have any recommendations as to how to proceed?  Any advice
would
be greatly appreciated.

                                         -Brian M.

/proc/cpuinfo:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 67
model name      : Dual-Core AMD Opteron(tm) Processor 1220
stepping        : 3
cpu MHz         : 2814.456
cache size      : 1024 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx
fxsr
sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
pni
cx16 lahf_lm cmp_legacy extapic cr8_legacy
bogomips        : 5630.48
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 67
model name      : Dual-Core AMD Opteron(tm) Processor 1220
stepping        : 3
cpu MHz         : 2814.456
cache size      : 1024 KB
physical id     : 0
siblings        : 1
core id         : 1
cpu cores       : 1
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx
fxsr
sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
pni
cx16 lahf_lm cmp_legacy extapic cr8_legacy
bogomips        : 5630.48
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc


_______________________________________________
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

Brian P. Martin

2009-Jul-27 20:54 UTC

head link

RE: [Xen-users] SVM not detected on Opteron 1220

Awesome, Doug!  I''ve been on that wild goose chase for quite a while.  

I''ve been trying to figure out why a DomU guest can''t see a
parallel port
(either the one on the mobo or another on a PCI card).  I thought it was
because I didn''t have SVM active for some reason.  I''m still
stuck, but at
least now I''m stuck on the right problem.  

The few minutes you spent responding has saved me many hours of wasted
effort.  Thanks a lot.

                               -Brian M.
> -----Original Message-----
> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> Sent: Monday, July 27, 2009 1:18 PM
> To: Brian P. Martin
> Cc: xen-users@lists.xensource.com
> Subject: RE: [Xen-users] SVM not detected on Opteron 1220
> 
> I believe this is normal (though I don''t have any AMD hardware, it
> should be the same as vmx flag on intel).  Xen masks certain bits in
> the
> cpu information, and Dom0 does not have direct access to the physical
> CPUs, only the virtual CPUs assigned by the hypervisor.
> 
> To verify you have svm enabled, you will want to look at the output of
> "xm info", specifically the line that starts
"xen_caps".  If you have
> entries there that start with "hvm" then your hardware supports
> virtualization.
> 
> Doug Magee
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Brian P.
> Martin
> Sent: Monday, July 27, 2009 2:14 PM
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] SVM not detected on Opteron 1220
> 
> I have SuperMicro mainboard, H8SMi-2 rev 2.01, with a dual core Opteron
> 1220
> processor.  I''ve verified that the BIOS had "Secure Virtual
Machine"
> enabled.  This appears to be the only virtualization option in the
> BIOS.
> I''m running xen 3.3.1 and kernel-xen-base 2.6.27.  When I boot up
the
> "svm"
> flag doesn''t appear in the /proc/cpuinfo flags area (full cpuinfo
shown
> at
> bottom).  In essence, it seems that the BIOS says virtualization is
> enabled,
> but Linux says it isn''t.
> 
> I tried updating the BIOS to the latest version, but that didn''t
change
> anything.
> Does anyone have any recommendations as to how to proceed?  Any advice
> would
> be greatly appreciated.
> 
>                                          -Brian M.
> 
> /proc/cpuinfo:
> 
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 67
> model name      : Dual-Core AMD Opteron(tm) Processor 1220
> stepping        : 3
> cpu MHz         : 2814.456
> cache size      : 1024 KB
> physical id     : 0
> siblings        : 1
> core id         : 0
> cpu cores       : 1
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx
> fxsr
> sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
> pni
> cx16 lahf_lm cmp_legacy extapic cr8_legacy
> bogomips        : 5630.48
> TLB size        : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp tm stc
> 
> processor       : 1
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 67
> model name      : Dual-Core AMD Opteron(tm) Processor 1220
> stepping        : 3
> cpu MHz         : 2814.456
> cache size      : 1024 KB
> physical id     : 0
> siblings        : 1
> core id         : 1
> cpu cores       : 1
> apicid          : 1
> initial apicid  : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx
> fxsr
> sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
> pni
> cx16 lahf_lm cmp_legacy extapic cr8_legacy
> bogomips        : 5630.48
> TLB size        : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp tm stc
> 
> 
> _______________________________________________
> 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

<djmagee@mageenet.net>

2009-Jul-28 12:20 UTC

head link

RE: [Xen-users] SVM not detected on Opteron 1220

No problem.

Your DomUs will only see the emulated hardware.  To see your real
hardware inside a DomU you will have to pass it through.  Without the
appropriate hardware, you''ll only be able to pass-through hardware to a
PV guest.  Since you''re on AMD, I''m going to have to assume
you don''t
have IOMMU hardware, as they haven''t sold any yet that I know.  Google
searches for the right keywords will reveal more than enough info you
can piece together to achieve this, but here''s a short summary:

Make sure pciback is available in your Dom0 kernel (either built-in or
as a module).
Identify PCI device you want to hide, likely using lspci
If pciback is builtin, then you''d have to add a
''pciback.hide=(...)'' to
the Dom0 kernel line in grub and restart
Otherwise, you can hide the device after startup as described here:
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_a
s_module
Assign the device to your DomU with a pci = [ ''...'' ] line the
domain''s
configuration file
 
I don''t have any experience with PV passthrough, but it should be
easier, though less stable/secure than HVM passthrough.  Also, lately,
xen pci pass-through development has focused mostly on iommu backed
passthrough, and I''ve read messages suggesting there are more
restrictions to pv passthrough in more recent versions of xen.

Good luck,
Doug Magee

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Brian P.
Martin
Sent: Monday, July 27, 2009 4:55 PM
To: djmagee@mageenet.net
Cc: xen-users@lists.xensource.com
Subject: RE: [Xen-users] SVM not detected on Opteron 1220

Awesome, Doug!  I''ve been on that wild goose chase for quite a while.  

I''ve been trying to figure out why a DomU guest can''t see a
parallel
port
(either the one on the mobo or another on a PCI card).  I thought it was
because I didn''t have SVM active for some reason.  I''m still
stuck, but
at
least now I''m stuck on the right problem.  

The few minutes you spent responding has saved me many hours of wasted
effort.  Thanks a lot.

                               -Brian M.
> -----Original Message-----
> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> Sent: Monday, July 27, 2009 1:18 PM
> To: Brian P. Martin
> Cc: xen-users@lists.xensource.com
> Subject: RE: [Xen-users] SVM not detected on Opteron 1220
> 
> I believe this is normal (though I don''t have any AMD hardware, it
> should be the same as vmx flag on intel).  Xen masks certain bits in
> the
> cpu information, and Dom0 does not have direct access to the physical
> CPUs, only the virtual CPUs assigned by the hypervisor.
> 
> To verify you have svm enabled, you will want to look at the output of
> "xm info", specifically the line that starts
"xen_caps".  If you have
> entries there that start with "hvm" then your hardware supports
> virtualization.
> 
> Doug Magee
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Brian P.
> Martin
> Sent: Monday, July 27, 2009 2:14 PM
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] SVM not detected on Opteron 1220
> 
> I have SuperMicro mainboard, H8SMi-2 rev 2.01, with a dual core
Opteron> 1220
> processor.  I''ve verified that the BIOS had "Secure Virtual
Machine"
> enabled.  This appears to be the only virtualization option in the
> BIOS.
> I''m running xen 3.3.1 and kernel-xen-base 2.6.27.  When I boot up
the
> "svm"
> flag doesn''t appear in the /proc/cpuinfo flags area (full cpuinfo
shown> at
> bottom).  In essence, it seems that the BIOS says virtualization is
> enabled,
> but Linux says it isn''t.
> 
> I tried updating the BIOS to the latest version, but that didn''t
change> anything.
> Does anyone have any recommendations as to how to proceed?  Any advice
> would
> be greatly appreciated.
> 
>                                          -Brian M.
> 
> /proc/cpuinfo:
> 
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 67
> model name      : Dual-Core AMD Opteron(tm) Processor 1220
> stepping        : 3
> cpu MHz         : 2814.456
> cache size      : 1024 KB
> physical id     : 0
> siblings        : 1
> core id         : 0
> cpu cores       : 1
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush
mmx> fxsr
> sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
> pni
> cx16 lahf_lm cmp_legacy extapic cr8_legacy
> bogomips        : 5630.48
> TLB size        : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp tm stc
> 
> processor       : 1
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 67
> model name      : Dual-Core AMD Opteron(tm) Processor 1220
> stepping        : 3
> cpu MHz         : 2814.456
> cache size      : 1024 KB
> physical id     : 0
> siblings        : 1
> core id         : 1
> cpu cores       : 1
> apicid          : 1
> initial apicid  : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush
mmx> fxsr
> sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
> pni
> cx16 lahf_lm cmp_legacy extapic cr8_legacy
> bogomips        : 5630.48
> TLB size        : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp tm stc
> 
> 
> _______________________________________________
> 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

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brian P. Martin

2009-Jul-29 04:31 UTC

head link

[Xen-users] DomU can''t access PCI Parallel port (was SVM not detected on Opteron 1220)

Doug,
> 
> Your DomUs will only see the emulated hardware.  To see your real
> hardware inside a DomU you will have to pass it through.  Without the
> appropriate hardware, you''ll only be able to pass-through hardware
to a
> PV guest.  Since you''re on AMD, I''m going to have to
assume you don''t
> have IOMMU hardware, as they haven''t sold any yet that I know. 
Google
> searches for the right keywords will reveal more than enough info you
> can piece together to achieve this, but here''s a short summary:
> 
> Make sure pciback is available in your Dom0 kernel (either built-in or
> as a module).
> Identify PCI device you want to hide, likely using lspci
> If pciback is builtin, then you''d have to add a
''pciback.hide=(...)'' to
> the Dom0 kernel line in grub and restart
> Otherwise, you can hide the device after startup as described here:
> http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_
> a
> s_module
> Assign the device to your DomU with a pci = [ ''...'' ]
line the domain''s
> configuration file
> 
> I don''t have any experience with PV passthrough, but it should be
> easier, though less stable/secure than HVM passthrough.  Also, lately,
> xen pci pass-through development has focused mostly on iommu backed
> passthrough, and I''ve read messages suggesting there are more
> restrictions to pv passthrough in more recent versions of xen.
> 
Thanks for the great summary.  I''ve already been through this, but your
list
helped me check my work.  DomU still seems to know that the device is there,
but can''t talk to it.  In addition to the pci= statement, do I need to
map
IOPORTs and/or IRQs? 

                                 -Brian


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

<djmagee@mageenet.net>

2009-Jul-29 15:23 UTC

head link

[Xen-users] RE: DomU can''t access PCI Parallel port (was SVM not detected on Opteron 1220)

As far as I know there''s no way to explicitly map ioports or irqs;
xen/dom0 takes care of this for you.  There has been some discussion
lately about IRQ sharing and PV passthrough, as the requirements seem to
change with versions of xen. (Most development seems to be geared
towards iommu assisted passthrough.)  You may have to fiddle with
pciback.permissive settings, but I have no experience needing to do this
so I couldn''t tell you what the procedure is.

The best way to get help from this list will be to post all the relevant
logs and configuration files you have.  This includes your
/var/log/xen/qemu-...log for the domain, and any relevant system
messages in the domu.  I''d include lspci -vvv output from the domu, and
try to see if you get any messages when you load the appropriate driver
for the card in domu, for example, check dmesg or syslog after a
modprobe parport (or whatever the driver is, it''s been years since
I''ve
used anything on a parallel port), and see if there''s any output
whatsoever pertaining to your device.

-----Original Message-----
From: Brian P. Martin [mailto:Brian@MartinConsulting.com] 
Sent: Wednesday, July 29, 2009 12:31 AM
To: djmagee@mageenet.net
Cc: xen-users@lists.xensource.com
Subject: DomU can''t access PCI Parallel port (was SVM not detected on
Opteron 1220)

Doug,
> 
> Your DomUs will only see the emulated hardware.  To see your real
> hardware inside a DomU you will have to pass it through.  Without the
> appropriate hardware, you''ll only be able to pass-through hardware
to
a> PV guest.  Since you''re on AMD, I''m going to have to
assume you don''t
> have IOMMU hardware, as they haven''t sold any yet that I know. 
Google
> searches for the right keywords will reveal more than enough info you
> can piece together to achieve this, but here''s a short summary:
> 
> Make sure pciback is available in your Dom0 kernel (either built-in or
> as a module).
> Identify PCI device you want to hide, likely using lspci
> If pciback is builtin, then you''d have to add a
''pciback.hide=(...)''
to> the Dom0 kernel line in grub and restart
> Otherwise, you can hide the device after startup as described here:
>
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_> a
> s_module
> Assign the device to your DomU with a pci = [ ''...'' ]
line the
domain''s> configuration file
> 
> I don''t have any experience with PV passthrough, but it should be
> easier, though less stable/secure than HVM passthrough.  Also, lately,
> xen pci pass-through development has focused mostly on iommu backed
> passthrough, and I''ve read messages suggesting there are more
> restrictions to pv passthrough in more recent versions of xen.
> 
Thanks for the great summary.  I''ve already been through this, but your
list
helped me check my work.  DomU still seems to know that the device is
there,
but can''t talk to it.  In addition to the pci= statement, do I need to
map
IOPORTs and/or IRQs? 

                                 -Brian


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brian P. Martin

2009-Aug-05 17:34 UTC

head link

[Xen-users] RE: DomU can''t access PCI Parallel port

> The best way to get help from this list will be to post all the
> relevant logs and configuration files you have.  
To summarize the problem:  I''ve been stuck for several weeks with a Xen
problem at a client site.  I have a domU guest that needs access to a
parallel port for an old license dongle.  I''ve tried both an on-board
parallel port, and currently a PCI card without success.  

Currently, as a diagnostic move to make sure this isn''t a guest OS
problem,
I''m booting up Knoppix as the guest.  I''ve also replaced the
dongle with an
HP Laserjet 4 printer, so we can ignore any dongle-specific issues.

The original OS (Win2K) seems to know the PCI parallel port is there, but
can''t talk to it (ParVDM error 2 - unable to get device object pointer
for
port object).  I tried the normal fixes for that error without success.

Knoppix 5.1.1 can''t see the device at all (nothing from lspci or
/proc/ioports, either with or without pci=routeirq).  

Below are the relevant files and info.  I''m really stuck on this, and
could
use some help figuring it out.  I think I''m close, but I''ve
missed a step
somewhere.

                           -Brian 

Version Info:
--------------------------------------------------------
openSUSE-release-11.1-1.18
xen-3.3.1_18546_16-0.1.1
kernel-xen-2.6.27.23-0.1.1


DomU configuration file:
--------------------------------------------------------
name="vsvr6"
uuid="e0cee623-aa8b-3932-62ad-22396dedc659"
memory=1536
maxmem=1536
vcpus=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="restart"
localtime=1
keymap="en-us"
builder="hvm"
extid=0
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="cd"
disk=[
''file:home/samba/common/downloads/Knoppix/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso
,hdc:cdrom,r'' ]
sdl=0
stdvga=0
vnc=1
vncconsole=0
vncdisplay=5
vncunused=1
apic=1
acpi=1
pae=0
usb=1
usbdevice=''tablet''
serial="pty"
pci = [ ''0000.01:02.0'' ]


My additions to /etc/modprobe.d/blacklist:
--------------------------------------------------------
blacklist lp
blacklist parport
blacklist parport_pc


/etc/modprobe.conf.local:
--------------------------------------------------------
options pciback hide=(0000:01:02.0)


Excerpt from Dom0 lspci -vvv:
--------------------------------------------------------
01:02.0 Parallel controller: AFAVLAB Technology Inc TK9902 (prog-if 02
[ECP])
        Subsystem: AFAVLAB Technology Inc TK9902
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at ec00 [size=8]
        Region 1: I/O ports at e880 [size=4]
        Capabilities: [a0] Power Management version 1
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Kernel modules: parport_pc

[Note: lsmod does not indicate that parport_pc is loaded, as it was before I
blacklisted it.]


qemu-dm-vsvr6.log:
--------------------------------------------------------
domid: 23                                 
qemu: the number of cpus is 1             
Watching /local/domain/0/device-model/23/logdirty/next-active
Watching /local/domain/0/device-model/23/command             
xs_read(): vncpasswd get error.
/vm/e0cee623-aa8b-3932-62ad-22396dedc659/vncpasswd.
char device redirected to /dev/pts/0

qemu_map_cache_init nr_buckets = 10000 size 3145728

/usr/src/packages/BUILD/xen-3.3.1-testing/tools/ioemu-dir/hw/xen_blktap.c:71
3: Init blktap pipes
shared page at pfn 5fffe

buffered io page at pfn 5fffc

Time offset set -25200

Register xen platform.

Done register platform.

medium change watch on `hdc'' (index: 0):
home/samba/common/downloads/Knoppix/KNOPPIX_V5.1.1CD-2007-01-04-EN.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

gpe_en_write: addr=0x1f6c, val=0x0.

gpe_sts_write: addr=0x1f68, val=0xff.

gpe_en_write: addr=0x1f6d, val=0x0.

gpe_sts_write: addr=0x1f69, val=0xff.

gpe_en_write: addr=0x1f6e, val=0x0.

gpe_sts_write: addr=0x1f6a, val=0xff.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0xff.
gpe_en_write: addr=0x1f6c, val=0x8.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
gpe_sts_write: addr=0x1f68, val=0xff.
gpe_sts_write: addr=0x1f69, val=0xff.
gpe_sts_write: addr=0x1f6a, val=0xff.
gpe_sts_write: addr=0x1f6b, val=0xff.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_sts_write: addr=0x1f68, val=0xff.
gpe_sts_write: addr=0x1f69, val=0xff.
gpe_sts_write: addr=0x1f6a, val=0xff.
gpe_sts_write: addr=0x1f6b, val=0xff.
shutdown requested in cpu_handle_ioreq
Issued domain 23 poweroff
track_dirty_vram(f0000000, 180) failed (-1, 3)



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Jul 2009 - SVM not detected on Opteron 1220

[Xen-users] SVM not detected on Opteron 1220

RE: [Xen-users] SVM not detected on Opteron 1220

RE: [Xen-users] SVM not detected on Opteron 1220

RE: [Xen-users] SVM not detected on Opteron 1220

[Xen-users] DomU can''t access PCI Parallel port (was SVM not detected on Opteron 1220)

[Xen-users] RE: DomU can''t access PCI Parallel port (was SVM not detected on Opteron 1220)

[Xen-users] RE: DomU can''t access PCI Parallel port