Sent: 08/29/2006
From: Slava Baturin
Message:true about real machine ... sadly enough VMWare can do it.
"Bill Grant" wrote:
Show quoted text
> There is no way to do that in a virtual machine because there is no way
> to do it in a real machine.
>
> Slava Baturin wrote:
> > Thanks a lot Bill,
> > Judging by the number of your responses you spend quite a time with
> > V-Server . ... Did you happen to ran across any tools to resize
> > virtual disks? It sounds pretty uncomfortable not to have an ability
> > to increase/decrease v-disk size once you set it up. Of course there
> > is a way to image it and restore it on the new v-disk with more
> > space, but not lots of ghosting software happy with 2k3 . especially
> > with OS disks. Any advice?
> >
> > Thanks
> >
> >
> > "Bill Grant" wrote:
> >
> >> The fact that they are virtual machines doesn't really make any
> >> difference in a situation like that. The traffic coming over the WAN
> >> link to a vm can be completely isolated from the NIC in the host
> >> machine. By that I mean that the NIC in the host machine can be
> >> dedicated to the vm and not seen by the host's IP stack. From the
> >> network properties of that NIC in the host OS, you clear all of the
> >> boxes except VMNS.
> >>
> >> How vulnerable your LAN is will depend on how you configure the
> >> multihomed machines which can see both LAN and WAN.
> >>
> >> Slava Baturin wrote:
> >>> How safe to keep host OS within LAN and expose guests to WAN? This
> >>> will really help with backup/recover/storage VMs.
> >>>
> >>> Does anybody tried or have any info on the following VS2005 setup:
> >>>
> >>> 2003 EE R2 - host - 1st NIC - LAN
> >>> 2003 EE R2 - guests - 2nd NIC - WAN
> >>>
> >>> How stable, secure and reliable is it? I know Microsoft tells it's
> >>> safe in terms of network isolation . but what about vulnerabilities?
> >>>
> >>> Thanks in advance
>
>
>
Sent: 08/30/2006
From: "Bill Grant" <not.available@online>
Message: The fact that they are virtual machines doesn't really make any
difference in a situation like that. The traffic coming over the WAN link to
a vm can be completely isolated from the NIC in the host machine. By that I
mean that the NIC in the host machine can be dedicated to the vm and not
seen by the host's IP stack. From the network properties of that NIC in the
host OS, you clear all of the boxes except VMNS.
How vulnerable your LAN is will depend on how you configure the
multihomed machines which can see both LAN and WAN.
Slava Baturin wrote:
Show quoted text
> How safe to keep host OS within LAN and expose guests to WAN? This
> will really help with backup/recover/storage VMs.
>
> Does anybody tried or have any info on the following VS2005 setup:
>
> 2003 EE R2 - host - 1st NIC - LAN
> 2003 EE R2 - guests - 2nd NIC - WAN
>
> How stable, secure and reliable is it? I know Microsoft tells it's
> safe in terms of network isolation . but what about vulnerabilities?
>
> Thanks in advance
Sent: 08/30/2006
From: "Bill Grant" <not.available@online>
Message: There is no way to do that in a virtual machine because there is no way
to do it in a real machine.
Slava Baturin wrote:
Show quoted text
> Thanks a lot Bill,
> Judging by the number of your responses you spend quite a time with
> V-Server . ... Did you happen to ran across any tools to resize
> virtual disks? It sounds pretty uncomfortable not to have an ability
> to increase/decrease v-disk size once you set it up. Of course there
> is a way to image it and restore it on the new v-disk with more
> space, but not lots of ghosting software happy with 2k3 . especially
> with OS disks. Any advice?
>
> Thanks
>
>
> "Bill Grant" wrote:
>
>> The fact that they are virtual machines doesn't really make any
>> difference in a situation like that. The traffic coming over the WAN
>> link to a vm can be completely isolated from the NIC in the host
>> machine. By that I mean that the NIC in the host machine can be
>> dedicated to the vm and not seen by the host's IP stack. From the
>> network properties of that NIC in the host OS, you clear all of the
>> boxes except VMNS.
>>
>> How vulnerable your LAN is will depend on how you configure the
>> multihomed machines which can see both LAN and WAN.
>>
>> Slava Baturin wrote:
>>> How safe to keep host OS within LAN and expose guests to WAN? This
>>> will really help with backup/recover/storage VMs.
>>>
>>> Does anybody tried or have any info on the following VS2005 setup:
>>>
>>> 2003 EE R2 - host - 1st NIC - LAN
>>> 2003 EE R2 - guests - 2nd NIC - WAN
>>>
>>> How stable, secure and reliable is it? I know Microsoft tells it's
>>> safe in terms of network isolation . but what about vulnerabilities?
>>>
>>> Thanks in advance
Sent: 08/30/2006
From: "Bill Grant" <not.available@online>
Message: If you regularly make a habit of getting this wrong and don't want to
use standard tools, then use VMWare!
Slava Baturin wrote:
Show quoted text
> true about real machine ... sadly enough VMWare can do it.
>
> "Bill Grant" wrote:
>
>> There is no way to do that in a virtual machine because there is
>> no way to do it in a real machine.
>>
>> Slava Baturin wrote:
>>> Thanks a lot Bill,
>>> Judging by the number of your responses you spend quite a time with
>>> V-Server . ... Did you happen to ran across any tools to resize
>>> virtual disks? It sounds pretty uncomfortable not to have an
>>> ability to increase/decrease v-disk size once you set it up. Of
>>> course there is a way to image it and restore it on the new v-disk
>>> with more space, but not lots of ghosting software happy with 2k3 .
>>> especially with OS disks. Any advice?
>>>
>>> Thanks
>>>
>>>
>>> "Bill Grant" wrote:
>>>
>>>> The fact that they are virtual machines doesn't really make any
>>>> difference in a situation like that. The traffic coming over the
>>>> WAN link to a vm can be completely isolated from the NIC in the
>>>> host machine. By that I mean that the NIC in the host machine can
>>>> be dedicated to the vm and not seen by the host's IP stack. From
>>>> the network properties of that NIC in the host OS, you clear all
>>>> of the boxes except VMNS.
>>>>
>>>> How vulnerable your LAN is will depend on how you configure
>>>> the multihomed machines which can see both LAN and WAN.
>>>>
>>>> Slava Baturin wrote:
>>>>> How safe to keep host OS within LAN and expose guests to WAN? This
>>>>> will really help with backup/recover/storage VMs.
>>>>>
>>>>> Does anybody tried or have any info on the following VS2005 setup:
>>>>>
>>>>> 2003 EE R2 - host - 1st NIC - LAN
>>>>> 2003 EE R2 - guests - 2nd NIC - WAN
>>>>>
>>>>> How stable, secure and reliable is it? I know Microsoft tells it's
>>>>> safe in terms of network isolation . but what about
>>>>> vulnerabilities?
>>>>>
>>>>> Thanks in advance
Sent: 08/30/2006
From: "Bill Grant" <not.available@online>
Message: That came across as pretty terse! My point really was that it is not
something that I would expect Virtual Server to do. If somebody writes some
third party software to do it, that's fine. But it is not something I would
expect to find as standard.
Bill Grant wrote:
Show quoted text
> If you regularly make a habit of getting this wrong and don't want
> to use standard tools, then use VMWare!
>
> Slava Baturin wrote:
>> true about real machine ... sadly enough VMWare can do it.
>>
>> "Bill Grant" wrote:
>>
>>> There is no way to do that in a virtual machine because there is
>>> no way to do it in a real machine.
>>>
>>> Slava Baturin wrote:
>>>> Thanks a lot Bill,
>>>> Judging by the number of your responses you spend quite a time with
>>>> V-Server . ... Did you happen to ran across any tools to resize
>>>> virtual disks? It sounds pretty uncomfortable not to have an
>>>> ability to increase/decrease v-disk size once you set it up. Of
>>>> course there is a way to image it and restore it on the new v-disk
>>>> with more space, but not lots of ghosting software happy with 2k3 .
>>>> especially with OS disks. Any advice?
>>>>
>>>> Thanks
>>>>
>>>>
>>>> "Bill Grant" wrote:
>>>>
>>>>> The fact that they are virtual machines doesn't really make
>>>>> any difference in a situation like that. The traffic coming over
>>>>> the WAN link to a vm can be completely isolated from the NIC in
>>>>> the host machine. By that I mean that the NIC in the host machine
>>>>> can be dedicated to the vm and not seen by the host's IP stack.
>>>>> From the network properties of that NIC in the host OS, you clear
>>>>> all of the boxes except VMNS.
>>>>>
>>>>> How vulnerable your LAN is will depend on how you configure
>>>>> the multihomed machines which can see both LAN and WAN.
>>>>>
>>>>> Slava Baturin wrote:
>>>>>> How safe to keep host OS within LAN and expose guests to WAN?
>>>>>> This will really help with backup/recover/storage VMs.
>>>>>>
>>>>>> Does anybody tried or have any info on the following VS2005
>>>>>> setup: 2003 EE R2 - host - 1st NIC - LAN
>>>>>> 2003 EE R2 - guests - 2nd NIC - WAN
>>>>>>
>>>>>> How stable, secure and reliable is it? I know Microsoft tells
>>>>>> it's safe in terms of network isolation . but what about
>>>>>> vulnerabilities?
>>>>>>
>>>>>> Thanks in advance
Wiki