← Back to team overview

openstack team mailing list archive

Re: [OpenStack] Files Injection in to Windows VMs

 

Thanks for link! By running the OpenHiddenSystemDrive exe, I am able to see
the injected file.

Regards,
Balu


On Thu, Apr 25, 2013 at 10:30 AM, Wangpan <hzwangpan@xxxxxxxxxxxxxxxx>wrote:

> **
> have you open and check the 'system reserved partition'? see the refer at
> bellow:
>
> http://www.techfeb.com/how-to-open-windows-7-hidden-system-reserved-partition/
>
> 2013-04-25
>  ------------------------------
>  Wangpan
>  ------------------------------
>  *发件人:*Balamurugan V G
> *发送时间:*2013-04-25 12:34
> *主题:*Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
> *收件人:*"Wangpan"<hzwangpan@xxxxxxxxxxxxxxxx>
> *抄送:*"openstack@xxxxxxxxxxxxxxxxxxx"<openstack@xxxxxxxxxxxxxxxxxxx>
>
>  Hi Wanpan,
>
> While I am able to inject files in to WindowsXP, CentOS5.9 and
> Ubuntu12.04. I am unable to do it for Windows8Entrprise OS. I did
> search the entire drive for the file I injected but couldnt file.
> Below is the log from nova-compute.log.
>
>
> 2013-04-24 01:41:27.973 AUDIT nova.compute.manager
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Starting instance...
> 2013-04-24 01:41:28.170 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Attempting claim:
> memory 1024 MB, disk 10 GB, VCPUs 1
> 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Memory: 3953
> MB, used: 2048 MB
> 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Memory limit: 5929
> MB, free: 3881 MB
> 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Disk: 225 GB,
> used: 15 GB
> 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Disk limit not
> specified, defaulting to unlimited
> 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total CPU: 2 VCPUs,
> used: 2 VCPUs
> 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] CPU limit not
> specified, defaulting to unlimited
> 2013-04-24 01:41:28.174 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Claim successful
> 2013-04-24 01:41:33.998 INFO nova.virt.libvirt.driver
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Creating image
> 2013-04-24 01:41:34.281 INFO nova.virt.libvirt.driver
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Injecting files into
> image 65eaa160-d0e7-403e-a52c-90bea3c22cf7
> 2013-04-24 01:41:36.534 INFO nova.virt.libvirt.firewall
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Called
> setup_basic_filtering in nwfilter
> 2013-04-24 01:41:36.535 INFO nova.virt.libvirt.firewall
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Ensuring static
> filters
> 2013-04-24 01:41:38.555 13316 INFO nova.compute.manager [-] Lifecycle
> event 0 on VM aa46445e-1f86-4a5a-8002-a7703ff98648
> 2013-04-24 01:41:38.763 13316 INFO nova.virt.libvirt.driver [-]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Instance spawned
> successfully.
> 2013-04-24 01:41:38.996 13316 INFO nova.compute.manager [-] [instance:
> aa46445e-1f86-4a5a-8002-a7703ff98648] During sync_power_state the
> instance has a pending task. Skip.
> 2013-04-24 01:41:59.494 13316 AUDIT nova.compute.resource_tracker [-]
> Auditing locally available compute resources
> 2013-04-24 01:42:00.345 13316 AUDIT nova.compute.resource_tracker [-]
> Free ram (MB): 881
> 2013-04-24 01:42:00.346 13316 AUDIT nova.compute.resource_tracker [-]
> Free disk (GB): 200
> 2013-04-24 01:42:00.346 13316 AUDIT nova.compute.resource_tracker [-]
> Free VCPUS: -1
> 2013-04-24 01:42:00.509 13316 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for openstack-dev:openstack-dev.com
> 2013-04-24 01:42:00.514 13316 INFO nova.compute.manager [-] Updating
> bandwidth usage cache
> 2013-04-24 01:43:06.442 13316 AUDIT nova.compute.resource_tracker [-]
> Auditing locally available compute resources
> 2013-04-24 01:43:07.041 13316 AUDIT nova.compute.resource_tracker [-]
> Free ram (MB): 881
> 2013-04-24 01:43:07.042 13316 AUDIT nova.compute.resource_tracker [-]
> Free disk (GB): 200
> 2013-04-24 01:43:07.042 13316 AUDIT nova.compute.resource_tracker [-]
> Free VCPUS: -1
> 2013-04-24 01:43:07.266 13316 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for openstack-dev:openstack-dev.com
>
> 2013-04-24 01:43:07.267 13316 INFO nova.compute.manager [-] Updating host status
>
> Regards,
> Balu
>
> On Wed, Apr 24, 2013 at 12:19 PM, Balamurugan V G
> <balamuruganvg@xxxxxxxxx> wrote:
> > Hi Wangpan,
> >
>
> > Thanks for the response. The file injection is actually working, sorry my
>
> > bad I was setting the dst-path incorrectly. I am using Nova 2013.1(Grizzly)
> > and Windows XP 32bit VM.
> >
> > When I used the following command, it worked:
> >
> > nova boot --flavor f43c36f9-de6a-42f4-bbbb-edcedafe371a --image
> > 3872c4c9-d8f7-4a18-a2cc-0406765d9379 --file balu.txt=balu.txt VM2
> >
> > The file balu.txt ended up in C: drive.
> >
> > Thanks again.
> >
> > Regards,
> > Balu
> >
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Apr 24, 2013 at 12:07 PM, Wangpan <hzwangpan@xxxxxxxxxxxxxxxx>
> > wrote:
> >>
> >> Hi Balamurugan,
> >> What the edition of nova you are running? is there any trace log in
> >> nova-compute.log(default path: /var/log/nova/nova-compute.log)?
>
> >> and what the edition of your windows VM(winxp/win7/win8)? if it is win7 or
>
> >> win8, the injected files may exist in the system reserved partition, you can
>
> >> google to open and check the injected files is there.(this may be a bug we
> >> need to fix)
> >>
> >>
> >> 2013-04-24
> >> ________________________________
> >> Wangpan
> >> ________________________________
> >> 发件人:Balamurugan V G
> >> 发送时间:2013-04-24 14:19
> >> 主题:[Openstack] [OpenStack] Files Injection in to Windows VMs
> >> 收件人:"openstack@xxxxxxxxxxxxxxxxxxx"<openstack@xxxxxxxxxxxxxxxxxxx>
> >> 抄送:
> >>
> >> Hi,
> >>
> >> I am able to get File Injection to work during a CentOS or Ubuntu VM
>
> >> instance creation. But it doesnt work for a Windows VM. Is there a way to
>
> >> get it to work for windows VM or it going to be a limitation we have to live
> >> with, perhaps due to filesystem differences?
> >>
> >> Regards,
> >> Balu
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
>

Follow ups

References