Howto hide scsi or other hardware from the virtual system

[Emre Bastuz]

Hi,

I have created a virtual system via xen and would like to strip some
unrequired virtual hardware from it.

Example: my virtual Windows system shows me a scsi PCI device (as
unknown device). I would like to get rid of it - I am only using IDE in
the virtual system.

How can I hide specific hardware from the virtual system?

Cheers,

Emre

P.S.: as far as I understand specifying "hide=<pci_id>" during boot of
the host system is only for hiding physical hardware from the *host*, so
it can be directly attached to a virtual system ... so "hide" is not
what I´m looking for (I guess)

--
http://www.emre.de                        UIN: 561260
PGP Key ID: 0xAFAC77FD

I don't see why some people even HAVE cars. -- Calvin

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

[Mr. Teo En Ming (Zhang Enming)-2]

Is it Xen pci device #0 under Other Devices in Device Manager of your Windows HVM domU?


--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com
Email: space.time.universe@...
MSN: teoenming@...
Mobile Phone: [phone]
Street: Bedok Reservoir Road
Republic of Singapore

On Sat, Oct 24, 2009 at 6:48 PM, Emre Bastuz <info@...> wrote:

Hi,

I have created a virtual system via xen and would like to strip some
unrequired virtual hardware from it.

Example: my virtual Windows system shows me a scsi PCI device (as
unknown device). I would like to get rid of it - I am only using IDE in
the virtual system.

How can I hide specific hardware from the virtual system?

Cheers,

Emre

P.S.: as far as I understand specifying "hide=<pci_id>" during boot of
the host system is only for hiding physical hardware from the *host*, so
it can be directly attached to a virtual system ... so "hide" is not
what I´m looking for (I guess)

--
http://www.emre.de                        UIN: 561260
PGP Key ID: 0xAFAC77FD

I don't see why some people even HAVE cars. -- Calvin

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

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

[Emre Bastuz]

Hi Teo,

Mr. Teo En Ming (Zhang Enming) schrieb:
> Is it Xen pci device #0 under Other Devices in Device Manager of your
> Windows HVM domU?

it´s PCI bus 0, device 3.

I had to use an additional tool "Everest" on Windows to identify the
unknown PCI device as the "XenSource PV SCSI Host Adapter" (device
manager just says "Unknown PCI").

Cheers,

Emre

--
http://www.emre.de                        UIN: 561260
PGP Key ID: 0xAFAC77FD

I don't see why some people even HAVE cars. -- Calvin

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

[Mr. Teo En Ming (Zhang Enming)-2]

Maybe you will want to install the Xen GPLPV drivers so that your unknown PCI device will be properly detected?

http://wiki.xensource.com/xenwiki/XenWindowsGplPv

--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com
Email: space.time.universe@...
MSN: teoenming@...
Mobile Phone: [phone]
Street: Bedok Reservoir Road
Republic of Singapore

On Sat, Oct 24, 2009 at 7:16 PM, Emre Bastuz <info@...> wrote:

Hi Teo,

Mr. Teo En Ming (Zhang Enming) schrieb:

> Is it Xen pci device #0 under Other Devices in Device Manager of your
> Windows HVM domU?

it´s PCI bus 0, device 3.

I had to use an additional tool "Everest" on Windows to identify the
unknown PCI device as the "XenSource PV SCSI Host Adapter" (device
manager just says "Unknown PCI").

Cheers,

Emre

--

http://www.emre.de                        UIN: 561260
PGP Key ID: 0xAFAC77FD

I don't see why some people even HAVE cars. -- Calvin

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

[Stefan Kuhne]

Emre Bastuz schrieb:

> Hi Teo,
>
> Mr. Teo En Ming (Zhang Enming) schrieb:
>> Is it Xen pci device #0 under Other Devices in Device Manager of your
>> Windows HVM domU?
>
> it´s PCI bus 0, device 3.
>
> I had to use an additional tool "Everest" on Windows to identify the
> unknown PCI device as the "XenSource PV SCSI Host Adapter" (device
> manager just says "Unknown PCI").
>

Have you installed gplpv drivers?

Stefan Kuhne



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

[Emre Bastuz]

Hi Teo,
hi Stefan,

thanks for the hints with the Xen Drivers for Windows! I´ll try that.

If it were possible to *not* provide SCSI to the virtual system in the
first place, that would be great. I am fond of keeping it simple :)

Cheers,

Emre

>
> --
> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical
> Engineering)
> Alma Maters:
> (1) Singapore Polytechnic
> (2) National University of Singapore
> Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com
> Email: space.time.universe@... <mailto:space.time.universe@...>
> MSN: teoenming@... <mailto:teoenming@...>
> Mobile Phone: [phone]
> Street: Bedok Reservoir Road
> Republic of Singapore
>
> On Sat, Oct 24, 2009 at 7:16 PM, Emre Bastuz <info@...
> <mailto:info@...>> wrote:
>
>     Hi Teo,
>
>     Mr. Teo En Ming (Zhang Enming) schrieb:
>     > Is it Xen pci device #0 under Other Devices in Device Manager of your
>     > Windows HVM domU?
>
>     it´s PCI bus 0, device 3.
>
>     I had to use an additional tool "Everest" on Windows to identify the
>     unknown PCI device as the "XenSource PV SCSI Host Adapter" (device
>     manager just says "Unknown PCI").
>
>     Cheers,
>
>     Emre
>
>     --
>     http://www.emre.de                        UIN: 561260
>     PGP Key ID: 0xAFAC77FD
>
>     I don't see why some people even HAVE cars. -- Calvin
>
>
>
>
>

--
http://www.emre.de                        UIN: 561260
PGP Key ID: 0xAFAC77FD

I don't see why some people even HAVE cars. -- Calvin

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

[이동규[NBP]]

It would take painful time if we go through each configuration step of installing windows while we create a few hundreds of Windows VMs. In case of Linux VMs, it is not too hard to create large number of VMs because we easily mount VM images from Dom0 to changes system configurations such as IP, Hostname, Mac Address, etc.

Is it possible to copy Windows Images from template Windows Image and change their configurations from Dom0?
or RIS(Remote Installation Service)/WDS(Window Deployment Service)can be used in Xen Environment?

Any hints would be greatly appreciated.

Dongkyu Lee

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

[Fajar A. Nugraha-3]

2009/11/6 이동규[NBP] <dongq.lee@...>:
> Is it possible to copy Windows Images from template Windows Image and change their configurations from Dom0?
> or RIS(Remote Installation Service)/WDS(Window Deployment Service)can be used in Xen Environment?

WDS should work (haven't personally tested it though) as HVM guests
supports PXE boot. You probably still need to install PV drivers
manually afterwards.

When working with Win 2003/XP domUs, my favorite method is to clone a
"specially prepared" (as in it's set to use DHCP, not static IP
address :D ) existing domU disk image and use newsid to change SID and
hostname. Works like a charm. Newsid is currently retired (see
http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx)
but you could probably just change the hostname manually on first
boot.

For Vista/Win2008 you might want to look at sysprep (although a simple
disk clone and manual hostname change on first boot might also work).
Note that on some systems (tested on Win2008r2 trial) changing MAC
address for your NIC (which is necessary when cloning a machine
located on the same subnet) requires reactivation.

--
Fajar

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

[Dustin Henning]

        My Windows knowledge is a bit dated, but I can tells you that
sysprep was an option for WinXP as well.  After sysprep, you have to do the
final installation steps again (enter key, name host, set up network), but
drivers are maintained, so I should think you could install GPLPV drivers
before sysprep, but mileage would most certainly vary.  However, and more
importantly, I don't believe a new SID is generated when you change the
name of a host or even reactivate a host, so I don't think the very fact
that you cloned the image will give you a new SID (hence the sysprep and
newsid tools).  The only change that MIGHT affect the SID is joining /
disjoining a domain, and I am simply not certain on whether or not this
resets the SID, but I do believe I recall reading things that indicate that
it does.  It could be that the SID goes back to the original upon
disjoining and is only changed upon joining because the DC generates one,
if this is the case, I am not sure how the DC would treat having multiple
devices with the same original SID being joined simultaneously.  I'd
recommend using sysprep, as would Microsoft, but be aware you can only run
it like three times per install before it is disabled (if you keep your
master clone [and continue to use it without changing it and running
sysprep again], it will never have been run but once).  Also be aware that
you have to make the clone without having booted again because once you
boot, the SID is regenerated, so the master clone should be made and never
booted, only copied.
        Dustin

-----Original Message-----
From: xen-users-bounces@... [mailto:xen-users-bounces@lists.
xensource.com] On Behalf Of Fajar A. Nugraha
Sent: Friday, November 06, 2009 03:35
To: 이동규[NBP]
Cc: xen-users@...
Subject: Re: [Xen-users] Creating hundreds of Windows VMs

2009/11/6 이동규[NBP] <dongq.lee@...>:
> Is it possible to copy Windows Images from template Windows Image and
change their configurations from Dom0?
> or RIS(Remote Installation Service)/WDS(Window Deployment Service)can be
used in Xen Environment?

WDS should work (haven't personally tested it though) as HVM guests
supports PXE boot. You probably still need to install PV drivers
manually afterwards.

When working with Win 2003/XP domUs, my favorite method is to clone a
"specially prepared" (as in it's set to use DHCP, not static IP
address :D ) existing domU disk image and use newsid to change SID and
hostname. Works like a charm. Newsid is currently retired (see
http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx)
but you could probably just change the hostname manually on first
boot.

For Vista/Win2008 you might want to look at sysprep (although a simple
disk clone and manual hostname change on first boot might also work).
Note that on some systems (tested on Win2008r2 trial) changing MAC
address for your NIC (which is necessary when cloning a machine
located on the same subnet) requires reactivation.

--
Fajar

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



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

[Nick Couchman]

Yes, Sysprep maintains drivers.  Another good option for XP is nLite -
it's a free tool for customizing the Windows installation source and
creating a "gold disc" of sorts that has many of your Windows install
settings pre-defined.  nLite lets you add drivers (GPLPV drivers can be
added this way so that they are automatically installed as you install
Windows), patches (you can use the Microsoft Update Catalog to grab them
and integrate them), and other files and installs to the Windows source.
 You can also remove certain hardware support, remove services, and
customize some of the low-level Windows behavior.  Finally, if you have
a volume license, you can put in your volume license key along with
other ownership information so that several of the install steps are
skipped altogether.  There's also a version that I think is called
"vLite" for Vista customization.

I use a combination of nLite plus Sysprep to build my machine images -
I use nLite to create my custom install disc, I do my install, then use
Sysprep and copy the machine image to as many machines as I need to
run.

-Nick

>>> On 2009/11/06 at 06:23, "Dustin Henning"
<Dustin.Henning@...> wrote:
> My Windows knowledge is a bit dated, but I can tells you that
> sysprep was an option for WinXP as well.  After sysprep, you have to
do the
> final installation steps again (enter key, name host, set up
network), but
> drivers are maintained, so I should think you could install GPLPV
drivers
> before sysprep, but mileage would most certainly vary.  However, and
more
> importantly, I don't believe a new SID is generated when you change
the
> name of a host or even reactivate a host, so I don't think the very
fact
> that you cloned the image will give you a new SID (hence the sysprep
and
> newsid tools).  The only change that MIGHT affect the SID is joining
/
> disjoining a domain, and I am simply not certain on whether or not
this
> resets the SID, but I do believe I recall reading things that
indicate that
> it does.  It could be that the SID goes back to the original upon
> disjoining and is only changed upon joining because the DC generates
one,
> if this is the case, I am not sure how the DC would treat having
multiple
> devices with the same original SID being joined simultaneously.  I'd
> recommend using sysprep, as would Microsoft, but be aware you can
only run
> it like three times per install before it is disabled (if you keep
your
> master clone [and continue to use it without changing it and running
> sysprep again], it will never have been run but once).  Also be aware
that
> you have to make the clone without having booted again because once
you
> boot, the SID is regenerated, so the master clone should be made and
never
> booted, only copied.
> Dustin
>
> -----Original Message-----
> From: xen-users-bounces@...
[mailto:xen-users-bounces@lists.
> xensource.com] On Behalf Of Fajar A. Nugraha
> Sent: Friday, November 06, 2009 03:35
> To: 이동규[NBP]
> Cc: xen-users@...
> Subject: Re: [Xen-users] Creating hundreds of Windows VMs
>
> 2009/11/6 이동규[NBP] <dongq.lee@...>:
>> Is it possible to copy Windows Images from template Windows Image
and
> change their configurations from Dom0?
>> or RIS(Remote Installation Service)/WDS(Window Deployment
Service)can be
> used in Xen Environment?
>
> WDS should work (haven't personally tested it though) as HVM guests
> supports PXE boot. You probably still need to install PV drivers
> manually afterwards.
>
> When working with Win 2003/XP domUs, my favorite method is to clone
a
> "specially prepared" (as in it's set to use DHCP, not static IP
> address :D ) existing domU disk image and use newsid to change SID
and
> hostname. Works like a charm. Newsid is currently retired (see
>
http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx)
> but you could probably just change the hostname manually on first
> boot.
>
> For Vista/Win2008 you might want to look at sysprep (although a
simple
> disk clone and manual hostname change on first boot might also
work).

> Note that on some systems (tested on Win2008r2 trial) changing MAC
> address for your NIC (which is necessary when cloning a machine
> located on the same subnet) requires reactivation.
>
> --
> Fajar
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@...
> http://lists.xensource.com/xen-users
>
>
>

--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

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

[Emre Bastuz]

Hi,

just to answer my own question for the record ...

Emre Bastuz schrieb:
> How can I hide specific hardware from the virtual system?
> ...
> P.S.: as far as I understand specifying "hide=<pci_id>" during boot of
> the host system is only for hiding physical hardware from the *host*, so
> it can be directly attached to a virtual system ... so "hide" is not
> what I´m looking for (I guess)

"hide" is the feature required here ... By "hiding" certain devices from
dom0 and *not* passing them to the domU, one can actually hide specific
devices from the virtual system.

Cheers,

Emre

--
http://www.emre.de                        UIN: 561260
PGP Key ID: 0xAFAC77FD

I don't see why some people even HAVE cars. -- Calvin

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

[Fajar A. Nugraha-3]

2009/11/6 Dustin Henning <Dustin.Henning@...>:
>        My Windows knowledge is a bit dated, but I can tells you that
> sysprep was an option for WinXP as well.  After sysprep, you have to do the
> final installation steps again (enter key, name host, set up network),

You're right, it does work. In fact it's probably the only method
supported by Microsoft.
The thing is it'd be MUCH easier to use newsid when working with
XP/Win2003. Which is why I didn't use sysprep for this purpose :)

> I don't think the very fact
> that you cloned the image will give you a new SID (hence the sysprep and
> newsid tools).

Correct. But for most purposes, having two windows hosts with the same
SID on the same network posses no harm (IMHO the technet blog explains
it best). Having the same host name, on the other hand, will surely
cause trouble (at the very least you get the annoying popup warning at
boot). Which is why I suggested that it might be enough to simply
change the host name (at least for XP).

For Win2008r2, since you have to reactivate anyway, it'd probably be
best to use sysprep.

> I'd
> recommend using sysprep, as would Microsoft, but be aware you can only run
> it like three times per install before it is disabled

that's the first time I've heard of that :D
Thanks for the info.

--
Fajar

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

[Andy Burns-8]

2009/11/9 Fajar A. Nugraha <fajar@...>:

> for most purposes, having two windows hosts with the same
> SID on the same network posses no harm (IMHO the technet blog explains
> it best). Having the same host name, on the other hand, will surely
> cause trouble

User accounts from different machines with identical SIDs will be
indistinguishable, you may or may not care about the security
implications.

If two or more machines with identical SIDs are members of a domain,
when one of them randomly changes the password on the computer
account, the other(s) will be locked out of the domain.

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