Laptop Setup
-
The last I've read, MS is allowing 4 instances of the same license[^] in a VM environment.
It's good to be alive
Turtle Hand wrote:
MS is allowing 4 instances of the same license[^] in a VM environment.
That's true if you're running Enterprise Edition. Standard Edition allows one instance, but since list price for Enterprise is four times list price for standard, it's pretty much the same thing.
-
Granted, this is a few years old, but now I am scared. http://www.hardwareanalysis.com/content/article/1795/[^] Do you know if drivers and support for Vista 64 bit are any better?
It's good to be alive
Don't forget that you can use drivers for Server 2003 for XP 64 bit.
-
As mentioned last week, I purchased a new Dell Latitude E6500, with a 4gb of RAM and 250gb of disk. My intent is to use Virtual PC to setup environments for each customer. As the base OS I plan on 64 bit Win XP. Then each virtual instance will have the OS of the customer. Can anyone see flaws in this idea? Does anyone have a better idea? Thanks in advance.
It's good to be alive
if you're only going to have one OS running at a time, then why not multi-boot?
-
Granted, this is a few years old, but now I am scared. http://www.hardwareanalysis.com/content/article/1795/[^] Do you know if drivers and support for Vista 64 bit are any better?
It's good to be alive
Vista licenses are 32/64 bit. I'd assume that since Vista64/4Gb ram is becoming a commonish config you'd have good luck finding drivers for your laptop. To be safe I'd pick a model that offered Vista64 as an installed option.
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains. -- Pride and Prejudice and Zombies
-
Don't forget that you can use drivers for Server 2003 for XP 64 bit.
-
if you're only going to have one OS running at a time, then why not multi-boot?
there are a lot of reasons not to multi-boot. - can only run OS at a time (the OP plans on running 2 at a time host + vm) - more hard drive space required. VM's emulate hardware so you can trick the OS into thinking it is on a 60gb partition when in fact it is only taking up 5-10gb on the hard disk. - windows multiboot doesn't like reinstallations. You must install the oldest OS first and if you need to reinstall an older one, all that were installed after it need to be reinstalled as well (or you hafta do some fixup with the boot records but I've never gotten that to work). - multiboot requires you to reboot when changing OS. VM doesn't. - VM allows for saved states. This is kinda like the last one but you don't have to wait on the hardware to boot. just click ON and the VM is ready in the last state that you left it. - REAL restore points. since everything is virtual, you can create a real restore point rather than the psuedo system restore point that microsoft offers in windows. - Can only have 4 (might no be 4 but it is a limited number) OS installed on a single HD. whereas VM allows as many as the hard drive will hold.
-
How often are server drivers provided for laptop hardware?
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains. -- Pride and Prejudice and Zombies
dan neely wrote:
How often are server drivers provided for laptop hardware?
Quite often. There's a lot of overlap between a blade server and a laptop these days. My point was that if you can't find a driver labelled as suitable for XP64, one labelled as suitable for Server 2003 (a mucb more common operating system) will probably work.
-
As mentioned last week, I purchased a new Dell Latitude E6500, with a 4gb of RAM and 250gb of disk. My intent is to use Virtual PC to setup environments for each customer. As the base OS I plan on 64 bit Win XP. Then each virtual instance will have the OS of the customer. Can anyone see flaws in this idea? Does anyone have a better idea? Thanks in advance.
It's good to be alive
I'm pretty sure that Virtual PC doesn't support 64bit clients. In fact, when I last tried it (about 6mo ago), there wasn't any VM software that would install XP64 in a client. Obviously you are talking about the host being XP64 and you hadn't specificly stated that you would be trying to run a 64bit client. But figured I would toss that out there just in case you aren't aware (in case any of your customers are running 64bit).
-
I'm pretty sure that Virtual PC doesn't support 64bit clients. In fact, when I last tried it (about 6mo ago), there wasn't any VM software that would install XP64 in a client. Obviously you are talking about the host being XP64 and you hadn't specificly stated that you would be trying to run a 64bit client. But figured I would toss that out there just in case you aren't aware (in case any of your customers are running 64bit).
kinar wrote:
In fact, when I last tried it (about 6mo ago), there wasn't any VM software that would install XP64 in a client.
Hyper-V will do this, and I think a full VMware ESX server will too. Of course, they cost a bit more than Virtual PC :)
-
Vista licenses are 32/64 bit. I'd assume that since Vista64/4Gb ram is becoming a commonish config you'd have good luck finding drivers for your laptop. To be safe I'd pick a model that offered Vista64 as an installed option.
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains. -- Pride and Prejudice and Zombies
I'm assuming that 64bits will let me use all 4 gb and perform faster as well. Maybe I need to bite the bullet with Vista.
It's good to be alive
-
dan neely wrote:
How often are server drivers provided for laptop hardware?
Quite often. There's a lot of overlap between a blade server and a laptop these days. My point was that if you can't find a driver labelled as suitable for XP64, one labelled as suitable for Server 2003 (a mucb more common operating system) will probably work.
Will these be listed officially, or will you either need to find a list for your model of someone who manually tried a bunch of likelyish looking server drivers, or beat your head off the wall doing the same?
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains. -- Pride and Prejudice and Zombies
-
I'm assuming that 64bits will let me use all 4 gb and perform faster as well. Maybe I need to bite the bullet with Vista.
It's good to be alive
-
I'm pretty sure that Virtual PC doesn't support 64bit clients. In fact, when I last tried it (about 6mo ago), there wasn't any VM software that would install XP64 in a client. Obviously you are talking about the host being XP64 and you hadn't specificly stated that you would be trying to run a 64bit client. But figured I would toss that out there just in case you aren't aware (in case any of your customers are running 64bit).
kinar wrote:
VM software that would install XP64 in a client
Eh? I haven't got a copy of XP64 but VMWare Workstation has handled everything I've thrown at it from x64 distros of Linux / Server 2003 + 2008 / Vista x64 and even Cosmos. To run 64-bit you do have to be running an x64 host.
I doubt it. If it isn't intuitive then we need to fix it. - Chris Maunder
-
I'm pretty sure that Virtual PC doesn't support 64bit clients. In fact, when I last tried it (about 6mo ago), there wasn't any VM software that would install XP64 in a client. Obviously you are talking about the host being XP64 and you hadn't specificly stated that you would be trying to run a 64bit client. But figured I would toss that out there just in case you aren't aware (in case any of your customers are running 64bit).
I have run win7 64bit and xp64 both under 64 bit linux using virtual box and vmware. I know kvm vmware esx and xen both support this but I have not tried them. I have also ran 64 bit linux under 64 bit windows.
John
modified on Monday, June 29, 2009 5:40 PM
-
kinar wrote:
VM software that would install XP64 in a client
Eh? I haven't got a copy of XP64 but VMWare Workstation has handled everything I've thrown at it from x64 distros of Linux / Server 2003 + 2008 / Vista x64 and even Cosmos. To run 64-bit you do have to be running an x64 host.
I doubt it. If it isn't intuitive then we need to fix it. - Chris Maunder
vmware server and player do allow running 64 bit xp, vista and win7 under them. So does virtualbox.
John
-
Will these be listed officially, or will you either need to find a list for your model of someone who manually tried a bunch of likelyish looking server drivers, or beat your head off the wall doing the same?
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains. -- Pride and Prejudice and Zombies
Usually, Server 2003 is listed as one of the offically supported operating systems.
-
As mentioned last week, I purchased a new Dell Latitude E6500, with a 4gb of RAM and 250gb of disk. My intent is to use Virtual PC to setup environments for each customer. As the base OS I plan on 64 bit Win XP. Then each virtual instance will have the OS of the customer. Can anyone see flaws in this idea? Does anyone have a better idea? Thanks in advance.
It's good to be alive
Turtle Hand wrote:
Then each virtual instance will have the OS of the customer.
Why not just one copy of each OS with each variation in service pack? I'm not sure what each customer is doing differently that you need to separate them. Or do you intend to get them to send you their environment changes as they alter them?
_____________________________ When life hands you marmots, make marmalade.
-
As mentioned last week, I purchased a new Dell Latitude E6500, with a 4gb of RAM and 250gb of disk. My intent is to use Virtual PC to setup environments for each customer. As the base OS I plan on 64 bit Win XP. Then each virtual instance will have the OS of the customer. Can anyone see flaws in this idea? Does anyone have a better idea? Thanks in advance.
It's good to be alive
Use VirtualBox (instead of VirtualPC) because it allows 64-bit clients. I'm running XP64 on my big bog, and have 32-bit and 64-bit virtual machines for XP, Vista, and Weven.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Use VirtualBox (instead of VirtualPC) because it allows 64-bit clients. I'm running XP64 on my big bog, and have 32-bit and 64-bit virtual machines for XP, Vista, and Weven.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Hadn't heard of Virtual Box until today. Thanks for the suggestion John, I'll look into it. At this point it looks like Vista 64 bits running Virtual Box.
It's good to be alive
-
Use VirtualBox (instead of VirtualPC) because it allows 64-bit clients. I'm running XP64 on my big bog, and have 32-bit and 64-bit virtual machines for XP, Vista, and Weven.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Hey John, I've installed Virtual Box today and have had nothing but trouble with it. It won't complete an install of XP or Vista. It runs into issues reading files from the CD. I've tried on two laptops with the same results. The forums have been a little help, but at this point I'm stuck and trying Virtual PC. Any thoughts?
It's good to be alive
